[jira] [Updated] (AMQ-9315) Add connectTimestamp to Connection and JMX view
[ https://issues.apache.org/jira/browse/AMQ-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-9315: Issue Type: Improvement (was: Task) > Add connectTimestamp to Connection and JMX view > --- > > Key: AMQ-9315 > URL: https://issues.apache.org/jira/browse/AMQ-9315 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Fix For: 6.0.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > > Add a timestamp to when a connection was added to the broker -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9301) Add additional fields to o.a.activemq.broker.jmx.Connection
[ https://issues.apache.org/jira/browse/AMQ-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-9301: Issue Type: Improvement (was: Task) > Add additional fields to o.a.activemq.broker.jmx.Connection > --- > > Key: AMQ-9301 > URL: https://issues.apache.org/jira/browse/AMQ-9301 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 6.0.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > > Add a few additional fields to JMX Connection object -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4415) org.apache.activemq.artemis.tests.integration.server.LVQTest#testMultipleMessages fails intermittently
[ https://issues.apache.org/jira/browse/ARTEMIS-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-4415: - Fix Version/s: 2.32.0 (was: 2.31.1) > org.apache.activemq.artemis.tests.integration.server.LVQTest#testMultipleMessages > fails intermittently > -- > > Key: ARTEMIS-4415 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4415 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Tests >Affects Versions: 2.30.0 >Reporter: Gary Tully >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.activemq.artemis.tests.integration.server.LVQTest#testMultipleMessages > it produces 4 messages in two last value groups and asserts that it can > consume the two last values in order. > on occasion it only sees the first values -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4444) Allow broker classpath extension using custom paths
[ https://issues.apache.org/jira/browse/ARTEMIS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-. Resolution: Fixed > Allow broker classpath extension using custom paths > --- > > Key: ARTEMIS- > URL: https://issues.apache.org/jira/browse/ARTEMIS- > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Currently users can add runtime dependencies by placing the jar files in the > `lib` directory of the broker distribution itself or in the `lib` directory > of the broker instance. Supporting an environment variable to extend the > classpath would avoid the need to copy those artifact in the broker > directories and allow to add those jar files to the ActiveMQ Artemis > container mounting additional volumes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4435) Some Artemis artifacts misses MANIFEST.MF content
[
https://issues.apache.org/jira/browse/ARTEMIS-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4435.
Resolution: Fixed
> Some Artemis artifacts misses MANIFEST.MF content
> -
>
> Key: ARTEMIS-4435
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4435
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.30.0
>Reporter: Chao Wang
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> These files are missing required values in MANIFEST.MF bundled within JAR:
> {code:java}
> ./org/apache/activemq/artemis-hornetq-protocol/2.31.0/artemis-hornetq-protocol-2.31.0.jar
> ./org/apache/activemq/artemis-hqclient-protocol/2.31.0/artemis-hqclient-protocol-2.31.0.jar
> {code}
> Required missing values:
> {code:java}
> Specification-Version:
> {code}
> This file is missing MANIFEST.MF completely:
> {code:java}
> ./org/apache/activemq/artemis-commons/2.31.0/artemis-commons-2.31.0.jar
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4449) [DOC] Fix url parameter separator in acceptor configuration
[
https://issues.apache.org/jira/browse/ARTEMIS-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4449.
Resolution: Fixed
> [DOC] Fix url parameter separator in acceptor configuration
> ---
>
> Key: ARTEMIS-4449
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4449
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Nandor Soma Abonyi
>Priority: Minor
> Fix For: 2.32.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When simply {{&}} is used in the xml configuration according to the
> [documentation|#configuring-netty-ssl], {{org.xml.sax.SAXParseException}}
> will occur. Instead {{&}} or simply {{;}} should be used. I prefer the latter
> as the default configuration uses that character anyway.
> Tldr. In case of
> {code:java}
> name="netty">tcp://localhost:61617?sslEnabled=true=/path
> {code}
> this error is raised:
> {code:java}
> Fatal Error] :182:83: The reference to entity "keyStorePath" must end with
> the ';' delimiter.
> org.xml.sax.SAXParseException; lineNumber: 182; columnNumber: 83; The
> reference to entity "keyStorePath" must end with the ';' delimiter.
> at
> java.xml/com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:262)
> at
> java.xml/com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:342)
> at
> org.apache.activemq.artemis.utils.XMLUtil.readerToElement(XMLUtil.java:91)
> at
> org.apache.activemq.artemis.utils.XMLUtil.streamToElement(XMLUtil.java:64)
> at
> org.apache.activemq.artemis.utils.XMLUtil.urlToElement(XMLUtil.java:73)
> at
> org.apache.activemq.artemis.core.config.FileDeploymentManager.readConfiguration(FileDeploymentManager.java:71)
> at
> org.apache.activemq.artemis.integration.FileBroker.createComponents(FileBroker.java:120)
> at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:119)
> at
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:214)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:164)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:144)
> at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:61)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4432) openwire connection failure handling is bypassing the actor and ignoring the operation context leading to contention in error
[ https://issues.apache.org/jira/browse/ARTEMIS-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4432. Resolution: Fixed > openwire connection failure handling is bypassing the actor and ignoring the > operation context leading to contention in error > - > > Key: ARTEMIS-4432 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4432 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: OpenWire >Affects Versions: 2.30.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.32.0 > > > On a kill -9 test, for a transacted batch openwire consumer, it is possibly > for a batch to get stuck in delivery due to contention on the current > transaction. A restart is needed to have redeliver happen in this case. > The contention can be avoided by respecting the ordered actor and operation > context in the fail handling that originates from the netty handler when a > connection dies due to socket error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4475. Resolution: Fixed > Upgrade ActiveMQ "Classic" to 5.17.6 > > > Key: ARTEMIS-4475 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4451) non-SASL AMQP connection fails if resource audit logging enabled
[ https://issues.apache.org/jira/browse/ARTEMIS-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4451. Resolution: Fixed > non-SASL AMQP connection fails if resource audit logging enabled > > > Key: ARTEMIS-4451 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4451 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > > If the resource audit logging is enabled, then previous connection related > audit log changes cause non-SASL AMQP connections to always fail, with the > broker indicating to the client that a SASL connection is required, even if > the broker config is actually such that it should not be. Simply disabling > the resource audit log in the logging config then allows the non-SASL > connection to succeed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4453) Bridge blocked by flow control, seemingly forever
[ https://issues.apache.org/jira/browse/ARTEMIS-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4453. Resolution: Fixed > Bridge blocked by flow control, seemingly forever > - > > Key: ARTEMIS-4453 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4453 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker, Clustering >Reporter: Andy Gustafson >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > I found what I believe to be a bug related to flow control with symmetric > clusters. I wrote [this > example|https://github.com/acgustafson/artemis-flowcontrol-issue] to > reproduce the behavior I am seeing. The test program does the following: > * Create 2 clustered embedded brokers > * Create 3000 topics with 1 producer per topic sending 1 message every 30 > seconds with 1500 producers on each broker. > * Create 12 consumers on a wildcard that matches all 3000 topics with 6 > consumers on each broker > * Create 1 additional "statistics" wildcard consumer to log how many > messages it has consumed over the previous 30 seconds > Shortly after running this program the "statistics consumer" shows it's only > consuming 1500 messages per 30 seconds. The broker's logs show the > $artemis.internal.sf queues are being blocked on flow control. From what I > can tell the broker never seems to recover from this, even after killing all > of the producers/consumers and restarting with a much lower number of > producers/consumers. > This behaviour started appearing for me in 2.22.0 after > https://issues.apache.org/jira/browse/ARTEMIS-3805 changed the default > producer-window-size to 1MB from -1. > > I can reproduce the issue using the latest snapshot. If you set the > producer-window-size back to -1 the issue no longer appears. In my test > program I used wildcards, but I was able to reproduce this without wildcards > as well. > > Program to reproduce: > [https://github.com/acgustafson/artemis-flowcontrol-issue] > > Discussion of this issue in slack at > [https://the-asf.slack.com/archives/CFL910J30/p1696356372797149?thread_ts=1694705189.957139=CFL910J30] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4446) Improve readability of code/config blocks in user manual
[ https://issues.apache.org/jira/browse/ARTEMIS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4446. Resolution: Fixed > Improve readability of code/config blocks in user manual > > > Key: ARTEMIS-4446 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4446 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Some code/config blocks in the user manual wrap around making them difficult > to read. Disable wrapping for such blocks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4447) Add paging prefetch parameters into address settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4447. Resolution: Fixed > Add paging prefetch parameters into address settings > > > Key: ARTEMIS-4447 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4447 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.31.0 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > we should include optimal prefetch values for paging. Right now the system > will always read up to max-read-page-messages and max-read-page-bytes. We > should have a separate configuration attribute for the prefetch value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4459) Broker should log when ignoring a duplicate MQTT QoS 2 message
[ https://issues.apache.org/jira/browse/ARTEMIS-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4459. Resolution: Fixed > Broker should log when ignoring a duplicate MQTT QoS 2 message > -- > > Key: ARTEMIS-4459 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4459 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4457) Upgrade jetty version to 10.0.16
[ https://issues.apache.org/jira/browse/ARTEMIS-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4457. Resolution: Fixed > Upgrade jetty version to 10.0.16 > > > Key: ARTEMIS-4457 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4457 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4434) Add extra logging.debug on Redistributor when redistribution is happening
[ https://issues.apache.org/jira/browse/ARTEMIS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4434. Resolution: Fixed > Add extra logging.debug on Redistributor when redistribution is happening > - > > Key: ARTEMIS-4434 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4434 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Priority: Trivial > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4461) Declare implicit dependencies for artemis-features
[
https://issues.apache.org/jira/browse/ARTEMIS-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4461.
Resolution: Fixed
> Declare implicit dependencies for artemis-features
> --
>
> Key: ARTEMIS-4461
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4461
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The {{artemis-features}} module has implicit dependencies which should be
> explicitly declared. If these dependencies are not explicitly declared then
> any system which parallelizes the project build (e.g.
> [mvnd|https://github.com/apache/maven-mvnd]) will fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4141) Message flow gets stuck
[ https://issues.apache.org/jira/browse/ARTEMIS-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4141. Resolution: Fixed > Message flow gets stuck > --- > > Key: ARTEMIS-4141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4141 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.22.0, 2.27.1 >Reporter: Ivan Iliev >Priority: Blocker > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Reproducible at > [https://github.com/iiliev2/activeqm-artemis/tree/main/sf-queue-stuck] - see > the readme. > Broader discussion of the issue at > https://the-asf.slack.com/archives/CFL910J30/p1673891918582619. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4450) Auto-deleted clustered destinations can cause message loss
[ https://issues.apache.org/jira/browse/ARTEMIS-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4450. Resolution: Fixed > Auto-deleted clustered destinations can cause message loss > -- > > Key: ARTEMIS-4450 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4450 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Anton Roskvist >Priority: Major > Fix For: 2.32.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > If a destination has a remote binding but not a local one, certain > MessageLoadBalancingTypes can cause message loss, transparent to the producer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4439) Upgrade Netty to 4.1.100.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4439. Resolution: Fixed > Upgrade Netty to 4.1.100.Final > -- > > Key: ARTEMIS-4439 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4439 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4467) Core client code visibility change required
[ https://issues.apache.org/jira/browse/ARTEMIS-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4467. Resolution: Fixed > Core client code visibility change required > --- > > Key: ARTEMIS-4467 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4467 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.31.0 >Reporter: Emmanuel Hugonnet >Priority: Major > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Some visibility changes are required to be able to use some core-client code > from the server if the classloader is not flat. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4464) Cleanup on Soak and Smoke Tests
[ https://issues.apache.org/jira/browse/ARTEMIS-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4464. Resolution: Fixed > Cleanup on Soak and Smoke Tests > --- > > Key: ARTEMIS-4464 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4464 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > I did the following cleanup: > - removed a few not used / ignored tests (DNSSwitchTest is not in use by any > CI I know any more and it's now vaporware) > - A lot of tests (too many) were using the maven CLi. I'm now calling the CLI > from the test > Keeping only a few that is either using a maven property or downloading jars. > - removed a few JMX usages and replaced by SimpleManagement (over messaging) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4442) Message Redistributor is leaking LinkedListImpl$Iterator
[ https://issues.apache.org/jira/browse/ARTEMIS-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4442. Resolution: Fixed > Message Redistributor is leaking LinkedListImpl$Iterator > > > Key: ARTEMIS-4442 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4442 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.31.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4466) Disable Artemis-features verification on non test profiles
[ https://issues.apache.org/jira/browse/ARTEMIS-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4466. Resolution: Fixed > Disable Artemis-features verification on non test profiles > -- > > Key: ARTEMIS-4466 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4466 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > > There's no need to run the Artemis-verification every time developers compile > the projects unless it is done for testing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4438) Upgrade JGroups to 5.3.0.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4438. Resolution: Fixed > Upgrade JGroups to 5.3.0.Final > -- > > Key: ARTEMIS-4438 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4438 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4443) properties config - support broker plugin - logging broker plugin
[
https://issues.apache.org/jira/browse/ARTEMIS-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4443.
Resolution: Fixed
> properties config - support broker plugin - logging broker plugin
> -
>
> Key: ARTEMIS-4443
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4443
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker, Configuration
>Affects Versions: 2.31.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> broker plugins require a way to add a new instance of a class to a collection
> via broker properties. Using the class name as the key can work nicely.
> In addition, the registration and configuration of broker plugins needs to be
> separated, currently they are handled in a single method call.
> {code}
> brokerPlugins.\"org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin.class\".init=LOG_ALL_EVENTS=false
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4456) Register metrics plugin
[ https://issues.apache.org/jira/browse/ARTEMIS-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4456. Resolution: Fixed > Register metrics plugin > --- > > Key: ARTEMIS-4456 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4456 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The metrics plugin needs a reference of ActiveMQServer to check its status > and avoid IllegalStateException during the startup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4471) Mark Artemis Maven Plugins as threadSafe=true
[ https://issues.apache.org/jira/browse/ARTEMIS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4471. Resolution: Fixed > Mark Artemis Maven Plugins as threadSafe=true > - > > Key: ARTEMIS-4471 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4471 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4474) Update to Zookeeper 3.8.3
[ https://issues.apache.org/jira/browse/ARTEMIS-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4474. Resolution: Fixed > Update to Zookeeper 3.8.3 > - > > Key: ARTEMIS-4474 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4474 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > Update to Zookeeper 3.8.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4437) Upgrade OWASP to 8.4.0
[ https://issues.apache.org/jira/browse/ARTEMIS-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4437. Resolution: Fixed > Upgrade OWASP to 8.4.0 > -- > > Key: ARTEMIS-4437 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4437 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4270) Messages get lost when using multiple consumers with topic hierarchies
[
https://issues.apache.org/jira/browse/ARTEMIS-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4270.
Resolution: Fixed
> Messages get lost when using multiple consumers with topic hierarchies
> --
>
> Key: ARTEMIS-4270
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4270
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMS
>Affects Versions: 2.24.0
>Reporter: Moritz
>Priority: Major
> Fix For: 2.32.0
>
> Attachments: topic-hierarchies-bug-updated.zip,
> topic-hierarchies-bug.zip
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> There is an issue when we have the following setup:
> * Shared durable consumer A listening to *news.#*
> * Shared durable consumer B listening to *news.europe.#*
> * Message M1 sent to *news.europe.sports*
> * Message M2 sent to *news.europe*
> Expected behavior:
> * A receives M1 and M2
> * B receives M1 and M2
> Actual behavior:
> * A receives M1 and M2
> * B receives M1
> This happens when it is run with a clean Artemis, i.e. without any previous
> data. If we run it a second time B receives M1 and M2. When using
> *consumer.receive()* it also works as expected.
>
> This also affects at least version *3.0.0-SNAPSHOT* however I couldn't select
> it so I chose the second version I've tested it for. The attached project
> showcases the bug where I simply adjusted the example
> {*}apache-artemis-3.0.0-SNAPSHOT/examples/features/standard/topic-hierarchies{*}.
> I couldn't test it with 2.29.0-SNAPSHOT since I would get exceptions
> concerning the topic not being multicast (already with the original example).
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4441) Add Docker chapter to User Manual
[ https://issues.apache.org/jira/browse/ARTEMIS-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4441. Resolution: Fixed > Add Docker chapter to User Manual > - > > Key: ARTEMIS-4441 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4441 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > > It would greatly improve user experience to have Docker info in the User > Manual rather than in its independent module as it is currently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4433) improve Reproducible Builds
[ https://issues.apache.org/jira/browse/ARTEMIS-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4433. Resolution: Fixed > improve Reproducible Builds > --- > > Key: ARTEMIS-4433 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4433 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.31.0 >Reporter: Herve Boutemy >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > there are 2 issues easy to fix: > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/activemq/artemis/README.md > - dependency-reduced-pom.xml stored in source-release archives > - old maven-rar-plugin > we'll see later for the remaining ones: we need to go step by step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic reopened ARTEMIS-4475: -- > Upgrade ActiveMQ "Classic" to 5.17.6 > > > Key: ARTEMIS-4475 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-4475: - Fix Version/s: 2.32.0 > Upgrade ActiveMQ "Classic" to 5.17.6 > > > Key: ARTEMIS-4475 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4461) Declare implicit dependencies for artemis-features
[
https://issues.apache.org/jira/browse/ARTEMIS-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4461.
> Declare implicit dependencies for artemis-features
> --
>
> Key: ARTEMIS-4461
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4461
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The {{artemis-features}} module has implicit dependencies which should be
> explicitly declared. If these dependencies are not explicitly declared then
> any system which parallelizes the project build (e.g.
> [mvnd|https://github.com/apache/maven-mvnd]) will fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4449) [DOC] Fix url parameter separator in acceptor configuration
[
https://issues.apache.org/jira/browse/ARTEMIS-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4449.
> [DOC] Fix url parameter separator in acceptor configuration
> ---
>
> Key: ARTEMIS-4449
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4449
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Nandor Soma Abonyi
>Priority: Minor
> Fix For: 2.32.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When simply {{&}} is used in the xml configuration according to the
> [documentation|#configuring-netty-ssl], {{org.xml.sax.SAXParseException}}
> will occur. Instead {{&}} or simply {{;}} should be used. I prefer the latter
> as the default configuration uses that character anyway.
> Tldr. In case of
> {code:java}
> name="netty">tcp://localhost:61617?sslEnabled=true=/path
> {code}
> this error is raised:
> {code:java}
> Fatal Error] :182:83: The reference to entity "keyStorePath" must end with
> the ';' delimiter.
> org.xml.sax.SAXParseException; lineNumber: 182; columnNumber: 83; The
> reference to entity "keyStorePath" must end with the ';' delimiter.
> at
> java.xml/com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:262)
> at
> java.xml/com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:342)
> at
> org.apache.activemq.artemis.utils.XMLUtil.readerToElement(XMLUtil.java:91)
> at
> org.apache.activemq.artemis.utils.XMLUtil.streamToElement(XMLUtil.java:64)
> at
> org.apache.activemq.artemis.utils.XMLUtil.urlToElement(XMLUtil.java:73)
> at
> org.apache.activemq.artemis.core.config.FileDeploymentManager.readConfiguration(FileDeploymentManager.java:71)
> at
> org.apache.activemq.artemis.integration.FileBroker.createComponents(FileBroker.java:120)
> at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:119)
> at
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:214)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:164)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:144)
> at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:61)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4457) Upgrade jetty version to 10.0.16
[ https://issues.apache.org/jira/browse/ARTEMIS-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4457. > Upgrade jetty version to 10.0.16 > > > Key: ARTEMIS-4457 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4457 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4438) Upgrade JGroups to 5.3.0.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4438. > Upgrade JGroups to 5.3.0.Final > -- > > Key: ARTEMIS-4438 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4438 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4435) Some Artemis artifacts misses MANIFEST.MF content
[
https://issues.apache.org/jira/browse/ARTEMIS-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4435.
Resolution: Fixed
> Some Artemis artifacts misses MANIFEST.MF content
> -
>
> Key: ARTEMIS-4435
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4435
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.30.0
>Reporter: Chao Wang
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> These files are missing required values in MANIFEST.MF bundled within JAR:
> {code:java}
> ./org/apache/activemq/artemis-hornetq-protocol/2.31.0/artemis-hornetq-protocol-2.31.0.jar
> ./org/apache/activemq/artemis-hqclient-protocol/2.31.0/artemis-hqclient-protocol-2.31.0.jar
> {code}
> Required missing values:
> {code:java}
> Specification-Version:
> {code}
> This file is missing MANIFEST.MF completely:
> {code:java}
> ./org/apache/activemq/artemis-commons/2.31.0/artemis-commons-2.31.0.jar
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4433) improve Reproducible Builds
[ https://issues.apache.org/jira/browse/ARTEMIS-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4433. > improve Reproducible Builds > --- > > Key: ARTEMIS-4433 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4433 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.31.0 >Reporter: Herve Boutemy >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > there are 2 issues easy to fix: > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/activemq/artemis/README.md > - dependency-reduced-pom.xml stored in source-release archives > - old maven-rar-plugin > we'll see later for the remaining ones: we need to go step by step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4475. Resolution: Fixed > Upgrade ActiveMQ "Classic" to 5.17.6 > > > Key: ARTEMIS-4475 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4451) non-SASL AMQP connection fails if resource audit logging enabled
[ https://issues.apache.org/jira/browse/ARTEMIS-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4451. > non-SASL AMQP connection fails if resource audit logging enabled > > > Key: ARTEMIS-4451 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4451 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > > If the resource audit logging is enabled, then previous connection related > audit log changes cause non-SASL AMQP connections to always fail, with the > broker indicating to the client that a SASL connection is required, even if > the broker config is actually such that it should not be. Simply disabling > the resource audit log in the logging config then allows the non-SASL > connection to succeed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4270) Messages get lost when using multiple consumers with topic hierarchies
[
https://issues.apache.org/jira/browse/ARTEMIS-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4270.
> Messages get lost when using multiple consumers with topic hierarchies
> --
>
> Key: ARTEMIS-4270
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4270
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMS
>Affects Versions: 2.24.0
>Reporter: Moritz
>Priority: Major
> Fix For: 2.32.0
>
> Attachments: topic-hierarchies-bug-updated.zip,
> topic-hierarchies-bug.zip
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> There is an issue when we have the following setup:
> * Shared durable consumer A listening to *news.#*
> * Shared durable consumer B listening to *news.europe.#*
> * Message M1 sent to *news.europe.sports*
> * Message M2 sent to *news.europe*
> Expected behavior:
> * A receives M1 and M2
> * B receives M1 and M2
> Actual behavior:
> * A receives M1 and M2
> * B receives M1
> This happens when it is run with a clean Artemis, i.e. without any previous
> data. If we run it a second time B receives M1 and M2. When using
> *consumer.receive()* it also works as expected.
>
> This also affects at least version *3.0.0-SNAPSHOT* however I couldn't select
> it so I chose the second version I've tested it for. The attached project
> showcases the bug where I simply adjusted the example
> {*}apache-artemis-3.0.0-SNAPSHOT/examples/features/standard/topic-hierarchies{*}.
> I couldn't test it with 2.29.0-SNAPSHOT since I would get exceptions
> concerning the topic not being multicast (already with the original example).
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4466) Disable Artemis-features verification on non test profiles
[ https://issues.apache.org/jira/browse/ARTEMIS-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4466. Resolution: Fixed > Disable Artemis-features verification on non test profiles > -- > > Key: ARTEMIS-4466 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4466 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Priority: Major > > There's no need to run the Artemis-verification every time developers compile > the projects unless it is done for testing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4441) Add Docker chapter to User Manual
[ https://issues.apache.org/jira/browse/ARTEMIS-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4441. Resolution: Fixed > Add Docker chapter to User Manual > - > > Key: ARTEMIS-4441 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4441 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > > It would greatly improve user experience to have Docker info in the User > Manual rather than in its independent module as it is currently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4459) Broker should log when ignoring a duplicate MQTT QoS 2 message
[ https://issues.apache.org/jira/browse/ARTEMIS-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4459. > Broker should log when ignoring a duplicate MQTT QoS 2 message > -- > > Key: ARTEMIS-4459 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4459 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4467) Core client code visibility change required
[ https://issues.apache.org/jira/browse/ARTEMIS-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4467. Resolution: Fixed > Core client code visibility change required > --- > > Key: ARTEMIS-4467 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4467 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.31.0 >Reporter: Emmanuel Hugonnet >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Some visibility changes are required to be able to use some core-client code > from the server if the classloader is not flat. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4471) Mark Artemis Maven Plugins as threadSafe=true
[ https://issues.apache.org/jira/browse/ARTEMIS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4471. Resolution: Fixed > Mark Artemis Maven Plugins as threadSafe=true > - > > Key: ARTEMIS-4471 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4471 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4450) Auto-deleted clustered destinations can cause message loss
[ https://issues.apache.org/jira/browse/ARTEMIS-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4450. Resolution: Fixed > Auto-deleted clustered destinations can cause message loss > -- > > Key: ARTEMIS-4450 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4450 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Anton Roskvist >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > If a destination has a remote binding but not a local one, certain > MessageLoadBalancingTypes can cause message loss, transparent to the producer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4141) Message flow gets stuck
[ https://issues.apache.org/jira/browse/ARTEMIS-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4141. > Message flow gets stuck > --- > > Key: ARTEMIS-4141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4141 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.22.0, 2.27.1 >Reporter: Ivan Iliev >Priority: Blocker > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Reproducible at > [https://github.com/iiliev2/activeqm-artemis/tree/main/sf-queue-stuck] - see > the readme. > Broader discussion of the issue at > https://the-asf.slack.com/archives/CFL910J30/p1673891918582619. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4432) openwire connection failure handling is bypassing the actor and ignoring the operation context leading to contention in error
[ https://issues.apache.org/jira/browse/ARTEMIS-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4432. > openwire connection failure handling is bypassing the actor and ignoring the > operation context leading to contention in error > - > > Key: ARTEMIS-4432 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4432 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: OpenWire >Affects Versions: 2.30.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.32.0 > > > On a kill -9 test, for a transacted batch openwire consumer, it is possibly > for a batch to get stuck in delivery due to contention on the current > transaction. A restart is needed to have redeliver happen in this case. > The contention can be avoided by respecting the ordered actor and operation > context in the fail handling that originates from the netty handler when a > connection dies due to socket error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4453) Bridge blocked by flow control, seemingly forever
[ https://issues.apache.org/jira/browse/ARTEMIS-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4453. Resolution: Fixed > Bridge blocked by flow control, seemingly forever > - > > Key: ARTEMIS-4453 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4453 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker, Clustering >Reporter: Andy Gustafson >Assignee: Justin Bertram >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > I found what I believe to be a bug related to flow control with symmetric > clusters. I wrote [this > example|https://github.com/acgustafson/artemis-flowcontrol-issue] to > reproduce the behavior I am seeing. The test program does the following: > * Create 2 clustered embedded brokers > * Create 3000 topics with 1 producer per topic sending 1 message every 30 > seconds with 1500 producers on each broker. > * Create 12 consumers on a wildcard that matches all 3000 topics with 6 > consumers on each broker > * Create 1 additional "statistics" wildcard consumer to log how many > messages it has consumed over the previous 30 seconds > Shortly after running this program the "statistics consumer" shows it's only > consuming 1500 messages per 30 seconds. The broker's logs show the > $artemis.internal.sf queues are being blocked on flow control. From what I > can tell the broker never seems to recover from this, even after killing all > of the producers/consumers and restarting with a much lower number of > producers/consumers. > This behaviour started appearing for me in 2.22.0 after > https://issues.apache.org/jira/browse/ARTEMIS-3805 changed the default > producer-window-size to 1MB from -1. > > I can reproduce the issue using the latest snapshot. If you set the > producer-window-size back to -1 the issue no longer appears. In my test > program I used wildcards, but I was able to reproduce this without wildcards > as well. > > Program to reproduce: > [https://github.com/acgustafson/artemis-flowcontrol-issue] > > Discussion of this issue in slack at > [https://the-asf.slack.com/archives/CFL910J30/p1696356372797149?thread_ts=1694705189.957139=CFL910J30] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4443) properties config - support broker plugin - logging broker plugin
[
https://issues.apache.org/jira/browse/ARTEMIS-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4443.
> properties config - support broker plugin - logging broker plugin
> -
>
> Key: ARTEMIS-4443
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4443
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker, Configuration
>Affects Versions: 2.31.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> broker plugins require a way to add a new instance of a class to a collection
> via broker properties. Using the class name as the key can work nicely.
> In addition, the registration and configuration of broker plugins needs to be
> separated, currently they are handled in a single method call.
> {code}
> brokerPlugins.\"org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin.class\".init=LOG_ALL_EVENTS=false
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4474) Update to Zookeeper 3.8.3
[ https://issues.apache.org/jira/browse/ARTEMIS-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4474. > Update to Zookeeper 3.8.3 > - > > Key: ARTEMIS-4474 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4474 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > Update to Zookeeper 3.8.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4444) Allow broker classpath extension using custom paths
[ https://issues.apache.org/jira/browse/ARTEMIS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-. Resolution: Fixed > Allow broker classpath extension using custom paths > --- > > Key: ARTEMIS- > URL: https://issues.apache.org/jira/browse/ARTEMIS- > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > Currently users can add runtime dependencies by placing the jar files in the > `lib` directory of the broker distribution itself or in the `lib` directory > of the broker instance. Supporting an environment variable to extend the > classpath would avoid the need to copy those artifact in the broker > directories and allow to add those jar files to the ActiveMQ Artemis > container mounting additional volumes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4447) Add paging prefetch parameters into address settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4447. Resolution: Fixed > Add paging prefetch parameters into address settings > > > Key: ARTEMIS-4447 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4447 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.31.0 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > we should include optimal prefetch values for paging. Right now the system > will always read up to max-read-page-messages and max-read-page-bytes. We > should have a separate configuration attribute for the prefetch value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4437) Upgrade OWASP to 8.4.0
[ https://issues.apache.org/jira/browse/ARTEMIS-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4437. > Upgrade OWASP to 8.4.0 > -- > > Key: ARTEMIS-4437 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4437 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4464) Cleanup on Soak and Smoke Tests
[ https://issues.apache.org/jira/browse/ARTEMIS-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4464. Resolution: Fixed > Cleanup on Soak and Smoke Tests > --- > > Key: ARTEMIS-4464 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4464 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > I did the following cleanup: > - removed a few not used / ignored tests (DNSSwitchTest is not in use by any > CI I know any more and it's now vaporware) > - A lot of tests (too many) were using the maven CLi. I'm now calling the CLI > from the test > Keeping only a few that is either using a maven property or downloading jars. > - removed a few JMX usages and replaced by SimpleManagement (over messaging) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4434) Add extra logging.debug on Redistributor when redistribution is happening
[ https://issues.apache.org/jira/browse/ARTEMIS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4434. Resolution: Fixed > Add extra logging.debug on Redistributor when redistribution is happening > - > > Key: ARTEMIS-4434 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4434 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Priority: Trivial > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4456) Register metrics plugin
[ https://issues.apache.org/jira/browse/ARTEMIS-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4456. Resolution: Fixed > Register metrics plugin > --- > > Key: ARTEMIS-4456 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4456 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > The metrics plugin needs a reference of ActiveMQServer to check its status > and avoid IllegalStateException during the startup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4446) Improve readability of code/config blocks in user manual
[ https://issues.apache.org/jira/browse/ARTEMIS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4446. Resolution: Fixed > Improve readability of code/config blocks in user manual > > > Key: ARTEMIS-4446 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4446 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Some code/config blocks in the user manual wrap around making them difficult > to read. Disable wrapping for such blocks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4475?focusedWorklogId=887229=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-887229 ] ASF GitHub Bot logged work on ARTEMIS-4475: --- Author: ASF GitHub Bot Created on: 25/Oct/23 17:39 Start Date: 25/Oct/23 17:39 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4654: URL: https://github.com/apache/activemq-artemis/pull/4654 Issue Time Tracking --- Worklog Id: (was: 887229) Time Spent: 20m (was: 10m) > Upgrade ActiveMQ "Classic" to 5.17.6 > > > Key: ARTEMIS-4475 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4467) Core client code visibility change required
[ https://issues.apache.org/jira/browse/ARTEMIS-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779593#comment-17779593 ] ASF subversion and git services commented on ARTEMIS-4467: -- Commit 37273701ea155b21c190341b397258abdcfaa5db in activemq-artemis's branch refs/heads/main from Emmanuel Hugonnet [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=37273701ea ] ARTEMIS-4467 Core client code visibility change required. * Since the constructors in RemotingConnectionImpl can be used from the server and the client. If the server calling code is in a different classloader then the constructor can't be called. * same for the 'active' boolean property of ActiveMQChannelHandler Issue: https://issues.apache.org/jira/browse/ARTEMIS-4467 Signed-off-by: Emmanuel Hugonnet > Core client code visibility change required > --- > > Key: ARTEMIS-4467 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4467 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.31.0 >Reporter: Emmanuel Hugonnet >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Some visibility changes are required to be able to use some core-client code > from the server if the classloader is not flat. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4467) Core client code visibility change required
[ https://issues.apache.org/jira/browse/ARTEMIS-4467?focusedWorklogId=887228=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-887228 ] ASF GitHub Bot logged work on ARTEMIS-4467: --- Author: ASF GitHub Bot Created on: 25/Oct/23 17:39 Start Date: 25/Oct/23 17:39 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4653: URL: https://github.com/apache/activemq-artemis/pull/4653 Issue Time Tracking --- Worklog Id: (was: 887228) Time Spent: 40m (was: 0.5h) > Core client code visibility change required > --- > > Key: ARTEMIS-4467 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4467 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.31.0 >Reporter: Emmanuel Hugonnet >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Some visibility changes are required to be able to use some core-client code > from the server if the classloader is not flat. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779594#comment-17779594 ] ASF subversion and git services commented on ARTEMIS-4475: -- Commit 28ac22e8925aba535089f6ee25b808144d7226c0 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=28ac22e892 ] ARTEMIS-4475 upgrade ActiveMQ 'Classic' to 5.17.6 > Upgrade ActiveMQ "Classic" to 5.17.6 > > > Key: ARTEMIS-4475 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4472) Diverts block when target address is not blocked
[
https://issues.apache.org/jira/browse/ARTEMIS-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779587#comment-17779587
]
Josh Reagan commented on ARTEMIS-4472:
--
Thanks for taking a look [~jbertram]. I think documenting would be acceptable
solution. Certainly preferred over anything that would negatively impact
performance. That said, can you think of any way to modify a message's routing
before it hits an address? The only thing I could think of was an interceptor.
But I'm not crazy about that solution as they're protocol dependent.
> Diverts block when target address is not blocked
>
>
> Key: ARTEMIS-4472
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4472
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.31.0
>Reporter: Josh Reagan
>Priority: Minor
>
> When using an exclusive divert with an {{address-full-policy}} set to
> {{BLOCK}}, the divert will become blocked when the source address reaches its
> limit. This happens even if the target address has space and is not blocked.
> For instance, if I have an address {{app.source-addr}}, and a divert picking
> up select messages from that source address and routing them to
> {{app.target-addr}}. If the address {{app.source-addr}} becomes full and
> blocks, producers are no longer able to send messages. Even though the
> messages they sent would be routed to the {{app.target-addr}}, and that
> address still has space available.
> Sample config:
> {code:xml}
>
>
> 5
> BLOCK
>
>
>
>
>
>
>
>
>
> app.source-addr
> app.target-addr
> true
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4475?focusedWorklogId=887223=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-887223 ] ASF GitHub Bot logged work on ARTEMIS-4475: --- Author: ASF GitHub Bot Created on: 25/Oct/23 17:02 Start Date: 25/Oct/23 17:02 Worklog Time Spent: 10m Work Description: jbertram opened a new pull request, #4654: URL: https://github.com/apache/activemq-artemis/pull/4654 (no comment) Issue Time Tracking --- Worklog Id: (was: 887223) Remaining Estimate: 0h Time Spent: 10m > Upgrade ActiveMQ "Classic" to 5.17.6 > > > Key: ARTEMIS-4475 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4475) Upgrade ActiveMQ "Classic" to 5.17.6
Justin Bertram created ARTEMIS-4475: --- Summary: Upgrade ActiveMQ "Classic" to 5.17.6 Key: ARTEMIS-4475 URL: https://issues.apache.org/jira/browse/ARTEMIS-4475 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4473) Diverts do not block when target address is full
[
https://issues.apache.org/jira/browse/ARTEMIS-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-4473:
Description:
When a message arrives on a source address, and is diverted to a target
address, the message will be routed to the target address even if that target
address is full and its address-full-policy is set to {{BLOCK}}. So if I have
an address {{app.source-addr}} which has space available. I can send messages
to it without issue. If that address has a divert configured to route the
messages to {{app.target-addr}}, they will be routed to that target address
without issue. Even if {{app.target-addr}} is full and is blocked.
Sample config:
{code:xml}
5
BLOCK
app.source-addr
app.target-addr
true
{code}
was:
When a message arrives on a source address, and is diverted to a target
address, the message will be routed to the target address even if that target
address is full and its address-full-policy is set to BLOCK. So if I have an
address "app.source-addr" which has space available. I can send messages to it
without issue. If that address has a divert configured to route the messages to
"app.target-addr", they will be routed to that target address without issue.
Even if "app.target-addr" is full and is blocked.
Sample config:
5
BLOCK
app.source-addr
app.target-addr
true
> Diverts do not block when target address is full
>
>
> Key: ARTEMIS-4473
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4473
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.31.0
>Reporter: Josh Reagan
>Priority: Minor
>
> When a message arrives on a source address, and is diverted to a target
> address, the message will be routed to the target address even if that target
> address is full and its address-full-policy is set to {{BLOCK}}. So if I have
> an address {{app.source-addr}} which has space available. I can send messages
> to it without issue. If that address has a divert configured to route the
> messages to {{app.target-addr}}, they will be routed to that target address
> without issue. Even if {{app.target-addr}} is full and is blocked.
> Sample config:
> {code:xml}
>
>
> 5
> BLOCK
>
>
>
>
>
>
>
>
>
> app.source-addr
> app.target-addr
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[
https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779556#comment-17779556
]
Petr Kuzel commented on ARTEMIS-4470:
-
_The receiver often thinks of the message as not only that immutable payload
from the sender, {+}but also various annotations supplied by the messaging
infrastructure along the way{+}._
--
[http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#section-message-format]
If stretching a lot, putObjectProperty could be for AMQP implemented as setting
an annotation.
> Headers loss in message sent from AMQP producer to AMQP consumer
>
>
> Key: ARTEMIS-4470
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4470
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
>Affects Versions: 2.31.0
>Reporter: Mohanavalli A
>Priority: Major
>
> Hi Team,
> Our message flow involves a AMQP Producer, Broker (with custom plugin) and a
> AMQP Consumer.
> The message is sent by Producer to TEST queue with few headers, the broker
> plugin adds few more headers on BeforeSend event on the TEST queue. When the
> message is consumed by the consumer from TEST we see loss of certain headers.
>
> We started facing this after the recent migration of the consumer from
> Openwire to AMQP protocol. There is no loss of header when the
> Producer/Consumer is on openwire.
>
> Scenario1
> --
> Producer(AMQP) to TEST
> Header1:String, Header2:long
>
> Plugin on BeforeSend event on TEST
> Adds two new headers PluginHeader1(String), PluginHeader2(long)
>
> Consumer(AMQP) from TEST
> Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing)
>
> Additional info:
> If browsing message in console on TEST: Headers :
> Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present)
> If the message is moved from TEST to TEST1 queue directly on the Web Console,
> the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue.
>
>
> Scenario2
> --
> Producer(AMQP)
> Header1:String, Header2:long
>
> Plugin
> Adds two new headers PluginHeader1(String), PluginHeader2(long)
>
> Consumer(Openwire)
> Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are
> present)
>
> Additional info:
> If browsing message in console on TEST: Headers :
> Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present)
> If the message is moved from TEST to TEST1 queue directly on the Web Console,
> the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue.
>
> Scenario3
> --
> Producer(Openwire)
> Header1:String, Header2:long
>
> Plugin
> Adds two new headers PluginHeader1(String), PluginHeader2(long)
>
> Consumer(AMQP)
> Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are
> present)
>
> Additional info:
> If browsing message in console on TEST: Headers :
> Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present)
> If the message is moved from TEST to TEST1 queue directly on the Web Console,
> all headers are present TEST1 queue.
>
> Thanks,
> Mohanavalli A
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779551#comment-17779551 ] Petr Kuzel commented on ARTEMIS-4470: - Thank you, the impl executes at the abstraction level of Artemis plugin. The Message interface abstracts the underlying protocols (it's apparently augmented by default reencode() at the AMQP introduction time). The AMQP specs primarily targets other interfaces. Granted that reconciling OpenWire, CORE and AMQP could be challenging and abstraction is not tiptop because of perf impact and plugin being a secondary interface. Best regards Kuzel > Headers loss in message sent from AMQP producer to AMQP consumer > > > Key: ARTEMIS-4470 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4470 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 2.31.0 >Reporter: Mohanavalli A >Priority: Major > > Hi Team, > Our message flow involves a AMQP Producer, Broker (with custom plugin) and a > AMQP Consumer. > The message is sent by Producer to TEST queue with few headers, the broker > plugin adds few more headers on BeforeSend event on the TEST queue. When the > message is consumed by the consumer from TEST we see loss of certain headers. > > We started facing this after the recent migration of the consumer from > Openwire to AMQP protocol. There is no loss of header when the > Producer/Consumer is on openwire. > > Scenario1 > -- > Producer(AMQP) to TEST > Header1:String, Header2:long > > Plugin on BeforeSend event on TEST > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) from TEST > Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > > Scenario2 > -- > Producer(AMQP) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(Openwire) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > Scenario3 > -- > Producer(Openwire) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > all headers are present TEST1 queue. > > Thanks, > Mohanavalli A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779546#comment-17779546 ] Timothy A. Bish commented on ARTEMIS-4470: -- It's going to depend on what you change in the Message, in AMQP the standard properties, application-properties, and application-data (the body) are considered immutable, but you have decided in a plugin you will violate that and mutate them, therefore the message must be re-encoded as internally those bits are treated as a binary blob that would be sent unchanged as they are by spec immutable. So this is not a drawback of AMQP is a consequence of your choice to mutate the immutable message portion en route. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#toc > Headers loss in message sent from AMQP producer to AMQP consumer > > > Key: ARTEMIS-4470 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4470 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 2.31.0 >Reporter: Mohanavalli A >Priority: Major > > Hi Team, > Our message flow involves a AMQP Producer, Broker (with custom plugin) and a > AMQP Consumer. > The message is sent by Producer to TEST queue with few headers, the broker > plugin adds few more headers on BeforeSend event on the TEST queue. When the > message is consumed by the consumer from TEST we see loss of certain headers. > > We started facing this after the recent migration of the consumer from > Openwire to AMQP protocol. There is no loss of header when the > Producer/Consumer is on openwire. > > Scenario1 > -- > Producer(AMQP) to TEST > Header1:String, Header2:long > > Plugin on BeforeSend event on TEST > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) from TEST > Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > > Scenario2 > -- > Producer(AMQP) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(Openwire) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > Scenario3 > -- > Producer(Openwire) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > all headers are present TEST1 queue. > > Thanks, > Mohanavalli A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4474) Update to Zookeeper 3.8.3
[ https://issues.apache.org/jira/browse/ARTEMIS-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4474. - Resolution: Fixed > Update to Zookeeper 3.8.3 > - > > Key: ARTEMIS-4474 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4474 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > Update to Zookeeper 3.8.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779538#comment-17779538 ] Petr Kuzel commented on ARTEMIS-4470: - Hi [~tabish] , the payload above is whole message including its body or just message headers, please? If the whole message including body then a huge drawback of the AMQP protocol, the OpenWire and CORE protocols do not need reencoding (default impl is empty body). Best regards Kuzel > Headers loss in message sent from AMQP producer to AMQP consumer > > > Key: ARTEMIS-4470 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4470 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 2.31.0 >Reporter: Mohanavalli A >Priority: Major > > Hi Team, > Our message flow involves a AMQP Producer, Broker (with custom plugin) and a > AMQP Consumer. > The message is sent by Producer to TEST queue with few headers, the broker > plugin adds few more headers on BeforeSend event on the TEST queue. When the > message is consumed by the consumer from TEST we see loss of certain headers. > > We started facing this after the recent migration of the consumer from > Openwire to AMQP protocol. There is no loss of header when the > Producer/Consumer is on openwire. > > Scenario1 > -- > Producer(AMQP) to TEST > Header1:String, Header2:long > > Plugin on BeforeSend event on TEST > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) from TEST > Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > > Scenario2 > -- > Producer(AMQP) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(Openwire) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > Scenario3 > -- > Producer(Openwire) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > all headers are present TEST1 queue. > > Thanks, > Mohanavalli A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4474) Update to Zookeeper 3.8.3
[ https://issues.apache.org/jira/browse/ARTEMIS-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779527#comment-17779527 ] ASF subversion and git services commented on ARTEMIS-4474: -- Commit 6649ecf9631424bfcc1ce8c2f7a1adcb28bd0008 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6649ecf963 ] ARTEMIS-4474: update to zookeeper 3.8.3 > Update to Zookeeper 3.8.3 > - > > Key: ARTEMIS-4474 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4474 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > Update to Zookeeper 3.8.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed ARTEMIS-4470. Resolution: Information Provided > Headers loss in message sent from AMQP producer to AMQP consumer > > > Key: ARTEMIS-4470 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4470 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 2.31.0 >Reporter: Mohanavalli A >Priority: Major > > Hi Team, > Our message flow involves a AMQP Producer, Broker (with custom plugin) and a > AMQP Consumer. > The message is sent by Producer to TEST queue with few headers, the broker > plugin adds few more headers on BeforeSend event on the TEST queue. When the > message is consumed by the consumer from TEST we see loss of certain headers. > > We started facing this after the recent migration of the consumer from > Openwire to AMQP protocol. There is no loss of header when the > Producer/Consumer is on openwire. > > Scenario1 > -- > Producer(AMQP) to TEST > Header1:String, Header2:long > > Plugin on BeforeSend event on TEST > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) from TEST > Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > > Scenario2 > -- > Producer(AMQP) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(Openwire) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > Scenario3 > -- > Producer(Openwire) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > all headers are present TEST1 queue. > > Thanks, > Mohanavalli A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779505#comment-17779505 ] Timothy A. Bish commented on ARTEMIS-4470: -- The method re-encodes the payload based on any changes and would not make sense to do on each add of a property as you would create a massive performance impact and increase GC overhead encoding and re-encoding with each property add or remove. > Headers loss in message sent from AMQP producer to AMQP consumer > > > Key: ARTEMIS-4470 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4470 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 2.31.0 >Reporter: Mohanavalli A >Priority: Major > > Hi Team, > Our message flow involves a AMQP Producer, Broker (with custom plugin) and a > AMQP Consumer. > The message is sent by Producer to TEST queue with few headers, the broker > plugin adds few more headers on BeforeSend event on the TEST queue. When the > message is consumed by the consumer from TEST we see loss of certain headers. > > We started facing this after the recent migration of the consumer from > Openwire to AMQP protocol. There is no loss of header when the > Producer/Consumer is on openwire. > > Scenario1 > -- > Producer(AMQP) to TEST > Header1:String, Header2:long > > Plugin on BeforeSend event on TEST > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) from TEST > Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > > Scenario2 > -- > Producer(AMQP) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(Openwire) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. > > Scenario3 > -- > Producer(Openwire) > Header1:String, Header2:long > > Plugin > Adds two new headers PluginHeader1(String), PluginHeader2(long) > > Consumer(AMQP) > Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are > present) > > Additional info: > If browsing message in console on TEST: Headers : > Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) > If the message is moved from TEST to TEST1 queue directly on the Web Console, > all headers are present TEST1 queue. > > Thanks, > Mohanavalli A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[
https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779498#comment-17779498
]
Petr Kuzel commented on ARTEMIS-4470:
-
Hi Timothy,
thx for the fast reaction, we've tried your hint and it helps a bit.
Now, looking at the method Javadoc at the interface, it's empty, the source
reads:
```
{color:#00} {color}{color:#7f0055}default{color}{color:#00}
{color}{color:#7f0055}void{color}{color:#00} reencode() {{color}
{color:#3f7f5f} // only valid probably on AMQP{color}
{color:#00} }{color}
{color:#00}```{color}
If you could clarify and commit its contract, please. Just in case it has some
other undesired effects or another method should be actually used or reencoding
setup should be a responsibility of putObjectProperty method itself.
Best regards
Kuzel
> Headers loss in message sent from AMQP producer to AMQP consumer
>
>
> Key: ARTEMIS-4470
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4470
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
>Affects Versions: 2.31.0
>Reporter: Mohanavalli A
>Priority: Major
>
> Hi Team,
> Our message flow involves a AMQP Producer, Broker (with custom plugin) and a
> AMQP Consumer.
> The message is sent by Producer to TEST queue with few headers, the broker
> plugin adds few more headers on BeforeSend event on the TEST queue. When the
> message is consumed by the consumer from TEST we see loss of certain headers.
>
> We started facing this after the recent migration of the consumer from
> Openwire to AMQP protocol. There is no loss of header when the
> Producer/Consumer is on openwire.
>
> Scenario1
> --
> Producer(AMQP) to TEST
> Header1:String, Header2:long
>
> Plugin on BeforeSend event on TEST
> Adds two new headers PluginHeader1(String), PluginHeader2(long)
>
> Consumer(AMQP) from TEST
> Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing)
>
> Additional info:
> If browsing message in console on TEST: Headers :
> Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present)
> If the message is moved from TEST to TEST1 queue directly on the Web Console,
> the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue.
>
>
> Scenario2
> --
> Producer(AMQP)
> Header1:String, Header2:long
>
> Plugin
> Adds two new headers PluginHeader1(String), PluginHeader2(long)
>
> Consumer(Openwire)
> Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are
> present)
>
> Additional info:
> If browsing message in console on TEST: Headers :
> Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present)
> If the message is moved from TEST to TEST1 queue directly on the Web Console,
> the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue.
>
> Scenario3
> --
> Producer(Openwire)
> Header1:String, Header2:long
>
> Plugin
> Adds two new headers PluginHeader1(String), PluginHeader2(long)
>
> Consumer(AMQP)
> Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are
> present)
>
> Additional info:
> If browsing message in console on TEST: Headers :
> Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present)
> If the message is moved from TEST to TEST1 queue directly on the Web Console,
> all headers are present TEST1 queue.
>
> Thanks,
> Mohanavalli A
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4474) Update to Zookeeper 3.8.3
Robbie Gemmell created ARTEMIS-4474: --- Summary: Update to Zookeeper 3.8.3 Key: ARTEMIS-4474 URL: https://issues.apache.org/jira/browse/ARTEMIS-4474 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.32.0 Update to Zookeeper 3.8.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4458) Upgrade Netty to 4.1.100.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4458?focusedWorklogId=887163=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-887163 ] ASF GitHub Bot logged work on ARTEMIS-4458: --- Author: ASF GitHub Bot Created on: 25/Oct/23 09:53 Start Date: 25/Oct/23 09:53 Worklog Time Spent: 10m Work Description: fredbalves86 commented on PR #4647: URL: https://github.com/apache/activemq-artemis/pull/4647#issuecomment-1778911230 Any ETA on 2.32.0 that will include this change? Issue Time Tracking --- Worklog Id: (was: 887163) Time Spent: 50m (was: 40m) > Upgrade Netty to 4.1.100.Final > -- > > Key: ARTEMIS-4458 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4458 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Emmanuel Hugonnet >Assignee: Justin Bertram >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9372) ActiveMQ fails to start - Looking for key xx but not found in fileMap
Md Fazle Ali created AMQ-9372:
-
Summary: ActiveMQ fails to start - Looking for key xx but not
found in fileMap
Key: AMQ-9372
URL: https://issues.apache.org/jira/browse/AMQ-9372
Project: ActiveMQ
Issue Type: Bug
Components: Broker, KahaDB
Affects Versions: 5.16.4
Reporter: Md Fazle Ali
Attachments: activemq.xml, image-2023-10-25-08-37-30-586.png,
image-2023-10-25-08-41-40-037.png, wrapper-1.log, wrapper.conf
We have recently upgraded to Apache ActiveMQ 5.16.4 in our production
environment. Since, the upgrade we face an issue.
We have setup the ActiveMQ as a Windows service which launches it through
wrapper.exe. The setup is same as it was before upgrade. There is no change in
setup after upgrade.
*Full Path to executable in service:*
D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\wrapper.exe -s
D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\wrapper.conf
set.ACTIVEMQ_HOME=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..
set.ACTIVEMQ_BASE=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..
!image-2023-10-25-08-37-30-586.png!
The kahadb store is at a high available file share.
\\kahadb\kahadb\data\kahadb
!image-2023-10-25-08-41-40-037.png!
Wrapper.conf and ActiveMq.xml is attached to the jira. Also full wrapper.log
file is attached.
We stop the Windows service everyday evening. It stops gracefully. After few
minutes we reboot the server (Windows server 2019). As Windows service StartUp
type is set to AUTOMATIC, the service starts executing. It launches wrapper.exe
to start ActiveMQ. But, ActiveMQ fails to start with following errors.
It looks for a data file and does not find it and gives a warning.
WARN | {color:#FF}Cannot recover message audit{color}
{quote}STATUS | wrapper | 2023/10/24 19:18:39 | --> Wrapper Started as Service
STATUS | wrapper | 2023/10/24 19:18:39 | Launching a JVM...
INFO | jvm 1 | 2023/10/24 19:18:43 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2023/10/24 19:18:43 | Copyright 1999-2006 Tanuki
Software, Inc. All Rights Reserved.
INFO | jvm 1 | 2023/10/24 19:18:43 |
INFO | jvm 1 | 2023/10/24 19:18:43 | Java Runtime: Red Hat, Inc. 1.8.0_345
D:\Summit\SummitTools6.3\openjdk-1.8_u345\jre
INFO | jvm 1 | 2023/10/24 19:18:43 | Heap sizes: current=5024768k
free=4762519k max=29826560k
INFO | jvm 1 | 2023/10/24 19:18:43 | JVM args:
-Dactivemq.home=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..
-Dactivemq.base=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..
-Djavax.net.ssl.keyStorePassword=actualpassword
-Djavax.net.ssl.trustStorePassword=actualpassword
-Djavax.net.ssl.keyStore=SumProdFil\\Summit\\Configuration\\ssl\\tomcat.ks
-Djavax.net.ssl.trustStore=SumProdFil\\Summit\\Configuration\\ssl\\java_trust_store.ks
-Dcom.sun.management.jmxremote
-Dorg.apache.activemq.UseDedicatedTaskRunner=true
-Djava.util.logging.config.file=logging.properties
-Dactivemq.conf=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\../conf
-Dactivemq.data=//KahaDB/KahaDB/data
-Djava.security.auth.login.config=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\../conf/login.config
-Xmx32g -Xms5g -Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.ssl=true
-Dcom.sun.management.jmxremote.password.file=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\../conf/jmx.password
-Dcom.sun.management.jmxremote.access.file=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\../conf/jmx.access
-Dcom.sun.management.jmxremote.rmi.port=49234
-Djava.library.path=D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\../bin/win64
-Dwrapper.key=q5RtUpLMae_kHike -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=5788
-Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE
-Dwrapper.cpu.timeout=0 -Dwrapper.jvmid=1
INFO | jvm 1 | 2023/10/24 19:18:43 | Extensions classpath:
INFO | jvm 1 | 2023/10/24 19:18:43 |
[D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..\lib,D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..\lib\camel,D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..\lib\optional,D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..\lib\web,D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..\lib\extra]
INFO | jvm 1 | 2023/10/24 19:18:43 | ACTIVEMQ_HOME:
D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..
INFO | jvm 1 | 2023/10/24 19:18:43 | ACTIVEMQ_BASE:
D:\Summit\SummitTools6.3\apache-activemq-5.16.4\bin\win64\..\..
INFO | jvm 1 | 2023/10/24 19:18:43 | ACTIVEMQ_CONF:
