[jira] [Closed] (ARTEMIS-4400) artemis-cdi-client: artemis-unit-test-support should be in test scope
[ https://issues.apache.org/jira/browse/ARTEMIS-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4400. Resolution: Fixed > artemis-cdi-client: artemis-unit-test-support should be in test scope > - > > Key: ARTEMIS-4400 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4400 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.30.0 >Reporter: Alexey Markevich >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.31.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The changes in ARTEMIS-4353 changed the artemis-cdi-client dependency on > artemis-unit-test-support from test scope to compile scope, but it should > clearly be in test scope so swap it back. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4427) MDB reusing Thread is using wrong transactionTimeout
[ https://issues.apache.org/jira/browse/ARTEMIS-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4427. Fix Version/s: 2.31.0 Resolution: Fixed > MDB reusing Thread is using wrong transactionTimeout > > > Key: ARTEMIS-4427 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4427 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: JMS >Affects Versions: 2.30.0 >Reporter: Emmanuel Hugonnet >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The wrong transactionTimeout being used by a MDB (that does not set an > explict transactionTimeout) in case it runs on a Thread where previously > another MDB with an explicitly set transactionTimetout was running. > https://issues.redhat.com/browse/WFLY-18433 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4378) Federation, ignore address policy when using pull consumer connection
[ https://issues.apache.org/jira/browse/ARTEMIS-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4378. Resolution: Fixed > Federation, ignore address policy when using pull consumer connection > -- > > Key: ARTEMIS-4378 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4378 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Federation >Affects Versions: 2.29.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Minor > Fix For: 2.31.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Using the batching pull consumer from ARTEMIS-4314 is only applicable to > queue Federation but both policies can be configured in the same federation. > If consumer window size of zero is configured any address policy should be > ignored. With address federation there is no local queue to gauge capacity > and messages will just accumate in the upstream. The concept of a pull > consumer for address federation does not make any sense. > This strategy is already adopted for queue Federation configured for > multicast addresses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4406) connection router LocalCache persisted entry tracking is not thread safe
[ https://issues.apache.org/jira/browse/ARTEMIS-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4406. Resolution: Fixed > connection router LocalCache persisted entry tracking is not thread safe > > > Key: ARTEMIS-4406 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4406 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Balancer >Affects Versions: 2.30.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The persistedCacheEntries map within LocalCache used to track persisted > entries for the connection router is a regular HashMap and so is not thread > safe, but it may be updated concurrently. Switch it to using a > ConcurrentHashMap. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4409) Update examples to use management.xml
[
https://issues.apache.org/jira/browse/ARTEMIS-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4409.
Resolution: Fixed
> Update examples to use management.xml
> -
>
> Key: ARTEMIS-4409
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4409
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the "client-kickoff" and "xa-heuristic" examples use System
> properties to configure remote JMX connectivity. This kind of configuration
> was made obsolete by {{management.xml}}, but the examples weren't updated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4349) Replace Guava cache with Caffeine
[ https://issues.apache.org/jira/browse/ARTEMIS-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4349. Resolution: Fixed > Replace Guava cache with Caffeine > - > > Key: ARTEMIS-4349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4349 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.30.0 >Reporter: Alexey Markevich >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.31.0 > > Time Spent: 10h 50m > Remaining Estimate: 0h > > based on benchmark https://github.com/ben-manes/caffeine/wiki/Benchmarks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-966) MQTT Session States do not survive a reboot
[ https://issues.apache.org/jira/browse/ARTEMIS-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-966. --- Resolution: Fixed > MQTT Session States do not survive a reboot > --- > > Key: ARTEMIS-966 > URL: https://issues.apache.org/jira/browse/ARTEMIS-966 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: MQTT >Reporter: Martyn Taylor >Assignee: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4396) Make address/queue "internal" property durable
[ https://issues.apache.org/jira/browse/ARTEMIS-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4396. Resolution: Fixed > Make address/queue "internal" property durable > -- > > Key: ARTEMIS-4396 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4396 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4408) Update docker-run.sh for overriding etc folder after instance creation
[ https://issues.apache.org/jira/browse/ARTEMIS-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4408. Fix Version/s: 2.31.0 Resolution: Fixed > Update docker-run.sh for overriding etc folder after instance creation > -- > > Key: ARTEMIS-4408 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4408 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4388) Add a test with TopicSubscription and redistribution OFF and OFF_WITH_REDISTRIBUTION
[ https://issues.apache.org/jira/browse/ARTEMIS-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4388. Resolution: Fixed > Add a test with TopicSubscription and redistribution OFF and > OFF_WITH_REDISTRIBUTION > > > Key: ARTEMIS-4388 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4388 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > > Topic subscription -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4401) Improving Paging & JDBC Performance
[ https://issues.apache.org/jira/browse/ARTEMIS-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4401. Resolution: Fixed > Improving Paging & JDBC Performance > --- > > Key: ARTEMIS-4401 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4401 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > Time Spent: 3h > Remaining Estimate: 0h > > Syncs are not properly implemented into page files. Basically ever message > sent and every blob update is issuing a sync update on the context and a > commit on the Database. > Certain databases will have an OK performance with lots of commits (e.g. > Postgres) but I'm not sure how correct is the blob update. > As part of this task I'm creating a few Database tests to validate these > changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4174) JMX RMI connector-ports limited to localhost listen for remote connections
[
https://issues.apache.org/jira/browse/ARTEMIS-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4174.
Resolution: Fixed
> JMX RMI connector-ports limited to localhost listen for remote connections
> --
>
> Key: ARTEMIS-4174
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4174
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.28.0
>Reporter: Marvin Blauth
>Priority: Minor
> Fix For: 2.31.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The documentation in docs/user-manual/en/management.md allows the
> interpretation that setting the connector-host of the "" element
> in management.xml could be used to limit the exposure of the JMX RMI TCP port
> to localhost only. It says the "connector-host" attribute for the
> "" element could be used to specify "the host to expose the agent
> on". Depending on the definition of the word "exposure" this may not be the
> case.
> The documentation in examples/features/standard/jmx-ssl/readme.md in contrast
> says 'To access this MBeanServer remotely, add the following to the
> management.xml configuration: connector-host="localhost"/>'. This is describing a remote connection using
> "localhost" in "connector-host", which at least would be in violation of my
> understanding of the notion of limiting exposure.
> Setting "connector-host" to "localhost" (which is the default) in fact leads
> to opening a port listening to all incoming external requests. This is due to
> creating an RMI registry in
> org.apache.activemq.artemis.core.server.management.RmiRegistryFactory.init()
> without providing a SocketFactory limiting the host.
> Example netstat output for such a setup:
> {noformat}
> $ netstat -tan | grep 1099 | grep LISTEN
> tcp6 0 0 :::1099 :::*LISTEN
> {noformat}
> It is unclear to me what the intended behavior is in terms of open TCP
> sockets. I assume a limitation of the exposure should be possible in my
> following suggestion for a solution (I can provide a patch, if this approach
> is to be taken).
>
> *Possible solution (if indeed desired this way)*
> If one wanted to expose the registry to the specified host only (not clear if
> that is the intended behavior as described above), a custom
> RMIServerSocketFactory could be created instead that only creates
> ServerSockets limited to the host name provided by the user in the
> "connector-host" attribute. This would then lead to the service only
> listening to the IP associated with the provided host name.
> Example netstat output using the same configuration but with the described
> change to the RmiRegistryFactory, showing the expected output:
> {noformat}
> $ netstat -tan | grep 1099 | grep LISTEN
> tcp6 0 0 127.0.0.1:1099 :::*LISTEN
> {noformat}
> A downside of this approach is that currently "localhost" seems to be the
> default value for connector-host if not explicitly set, see
> org.apache.activemq.artemis.core.config.JMXConnectorConfiguration. So a
> change in the semantics of the connector-host attributed would lead to a
> change of the behavior of users using this value implicitly. I assume that
> currently a remote login is not possible anyway if "localhost" is set, even
> though it is possible to initiate a TCP connection to the service, but I did
> not investigate this (note that this would be in contrast to the
> documentation cited above, so it should probably be investigated). If the
> assumption is indeed correct, the change in semantics should not negatively
> affect users.
>
> *Workaround*
> As workaround external connection attempts to the RMI ports can of course be
> dropped using a firewall.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4395) Upgrade example spring-boot-plugin version to 2.6.15
[ https://issues.apache.org/jira/browse/ARTEMIS-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4395. Resolution: Fixed > Upgrade example spring-boot-plugin version to 2.6.15 > > > Key: ARTEMIS-4395 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4395 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4369) add clarifying note to docs around transport options for broker-connections
[ https://issues.apache.org/jira/browse/ARTEMIS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4369. Resolution: Fixed > add clarifying note to docs around transport options for broker-connections > --- > > Key: ARTEMIS-4369 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4369 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Trivial > Fix For: 2.31.0 > > > Add clarifying note to the docs around URI transport options for > broker-connections, e.g enabling and configuration TLS, being the same as for > other connection URIs. Mention there is an example showing it in use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4389) The word "mesage" should be corrected to "message"
[ https://issues.apache.org/jira/browse/ARTEMIS-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4389. Fix Version/s: 2.31.0 Resolution: Fixed > The word "mesage" should be corrected to "message" > --- > > Key: ARTEMIS-4389 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4389 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Yashashree Chopada >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The mesage should change to a message for Activemq server logger code and a > few method names in the test case. > > For example - > https://github.com/apache/activemq-artemis/blob/ea1a55629919084e79cc3e2f0897983e95917c3a/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/ActiveMQServerLogger.java#L1565 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4428) Expand default loggers configuration
[
https://issues.apache.org/jira/browse/ARTEMIS-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4428.
Fix Version/s: 2.31.0
Resolution: Fixed
> Expand default loggers configuration
>
>
> Key: ARTEMIS-4428
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4428
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Environment: {code:java}
> rootLogger.level = OFF
> rootLogger.appenderRef.console.ref = console
> rootLogger.appenderRef.log_file.ref = log_file
> logger.audit_base.level = OFF
> logger.audit_base.appenderRef.audit_log_file.ref = audit_log_file
> logger.audit_resource.level = OFF
> logger.audit_resource.appenderRef.audit_log_file.ref = audit_log_file
> logger.audit_message.level = OFF
> logger.audit_message.appenderRef.audit_log_file.ref = audit_log_file
> {code}
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Some default loggers are defined using the compact configuration introduced
> in log4j 2.17.2, see
> https://logging.apache.org/log4j/2.x/manual/configuration.html#configuration-with-properties
> {code}
> rootLogger = INFO, console, log_file
> logger.audit_base = OFF, audit_log_file
> logger.audit_resource = OFF, audit_log_file
> logger.audit_message = OFF, audit_log_file
> {code}
> Expanding default loggers could improve readability, i.e.
> {code}
> rootLogger.level = OFF
> rootLogger.appenderRef.console.ref = console
> rootLogger.appenderRef.log_file.ref = log_file
> logger.audit_base.level = OFF
> logger.audit_base.appenderRef.audit_log_file.ref = audit_log_file
> logger.audit_resource.level = OFF
> logger.audit_resource.appenderRef.audit_log_file.ref = audit_log_file
> logger.audit_message.level = OFF
> logger.audit_message.appenderRef.audit_log_file.ref = audit_log_file
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3057) Provide alternative to max-disk-usage to measure by remaining disk free
[ https://issues.apache.org/jira/browse/ARTEMIS-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3057. Resolution: Fixed > Provide alternative to max-disk-usage to measure by remaining disk free > --- > > Key: ARTEMIS-3057 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3057 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.16.0 >Reporter: Barnaby Court >Assignee: Justin Bertram >Priority: Major > Labels: easy > Fix For: 2.31.0 > > Time Spent: 9h 10m > Remaining Estimate: 0h > > Today we can specify max-disk-usage as a percentage of disk that may be used > before blocking the queues. I believe this is done in order to prevent > journal corruption. Currently the value can be specified as a percentage > which works well for relatively small disks. When working on large systems > with many terabytes of storage even specifying 99% is going to result in > queues being blocked when there are still many gigabytes of disk space > remaining. > It would be very helpful to have an alternative version of the max-disk-usage > that allowed us to specify the threshold below which blocking should be > activated. For example, min-disk-available set to something like 500 > megabytes or 1 gigabyte before blocking the queues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4377) Add script for pushing docker images for a release
[ https://issues.apache.org/jira/browse/ARTEMIS-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4377. Fix Version/s: 2.31.0 Resolution: Fixed > Add script for pushing docker images for a release > -- > > Key: ARTEMIS-4377 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4377 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4372) Move CLI framework to picocli and implement auto-complete
[ https://issues.apache.org/jira/browse/ARTEMIS-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4372. Resolution: Fixed > Move CLI framework to picocli and implement auto-complete > - > > Key: ARTEMIS-4372 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4372 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > Time Spent: 6h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4419) Add broker federation support to the AMQP broker connection feature-set
[ https://issues.apache.org/jira/browse/ARTEMIS-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4419. Resolution: Fixed > Add broker federation support to the AMQP broker connection feature-set > > > Key: ARTEMIS-4419 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4419 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: AMQP >Affects Versions: 2.30.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.31.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Add a feature element to the broker connection feature-set that allows for > broker federation over AMQP on outgoing AMQP broker connections. The feature > should support duplex federation across the same connection allowing > configuration of federation for local address and queues from a remote and > the reverse. The AMQP broker connection configuration should be updated to > allow configuring this feature in XML and using the broker properties > mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4411) Change log level from ActiveMQRALogger.instantiatingDestination to DEBUG
[ https://issues.apache.org/jira/browse/ARTEMIS-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4411. Resolution: Fixed > Change log level from ActiveMQRALogger.instantiatingDestination to DEBUG > - > > Key: ARTEMIS-4411 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4411 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.30.0 >Reporter: George Gastaldi >Priority: Major > Fix For: 2.31.0 > > Time Spent: 10m > Remaining Estimate: 0h > > There are cases where JNDI isn't available, and this message is only useful > when debugging -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4425) Upgrade Hawtio to 2.17.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4425. Resolution: Fixed > Upgrade Hawtio to 2.17.6 > > > Key: ARTEMIS-4425 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4425 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4384) CLI method to verify topology on all the nodes (cluster verify)
[ https://issues.apache.org/jira/browse/ARTEMIS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4384. Resolution: Fixed > CLI method to verify topology on all the nodes (cluster verify) > --- > > Key: ARTEMIS-4384 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4384 > Project: ActiveMQ Artemis > Issue Type: New Feature >Affects Versions: 2.30.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > This CLI method will download the topology of a server, and connect to all > the individual nodes to verify their topology. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4370) Publishing message with existing topic alias and different topic causes message to be sent to incorrect topic
[
https://issues.apache.org/jira/browse/ARTEMIS-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4370.
Resolution: Fixed
> Publishing message with existing topic alias and different topic causes
> message to be sent to incorrect topic
> -
>
> Key: ARTEMIS-4370
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4370
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.29.0
>Reporter: Adam Zyzak
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> h3. Description
> When sending MQTT 5.0 publish message with topic alias number that has
> existing mapping for given connection and new topic, Artemis broker will
> incorrectly route message to topic from alias mapping instead of topic from
> publish message. This is incorrect behavior because broker should route
> message to topic from publish message and update alias mapping with new
> topic.
> Section 3.3.2.3.4 Topic Alias in MQTT 5.0 specification states the following:
> {code:java}
> A sender can modify the Topic Alias mapping by sending another PUBLISH in the
> same Network Connection with the same Topic Alias value and a different
> non-zero length Topic Name. {code}
>
> h3. Steps to reproduce
> # Create 2 MQTT subscribers: first on topic1 and second on topic2
> # Create 1 MQTT publisher
> # From publisher send publish message on topic1 with MQTT property
> TOPIC_ALIAS set to 1
> # From publisher send publish message on topic2 with MQTT property
> TOPIC_ALIAS set to 1
> h3. Current result
> First message is correctly routed to topic1, but second message is
> incorrectly routed to topic1 instead of topic2
> Method
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTPublishManager#sendToQueue
> adds mapping only if alias does not exist
> h3. Expected result
> Topic field in MQTT publish should have priority over TOPIC_ALIAS property.
> Topic alias stored under existing alias number should be updated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4382) CLI import / export may take a huge amount of time in large datasets.
[ https://issues.apache.org/jira/browse/ARTEMIS-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4382. Resolution: Fixed > CLI import / export may take a huge amount of time in large datasets. > - > > Key: ARTEMIS-4382 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4382 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.30.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4421) Page Counters are not working before rebuild is done
[ https://issues.apache.org/jira/browse/ARTEMIS-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4421. Resolution: Fixed > Page Counters are not working before rebuild is done > > > Key: ARTEMIS-4421 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4421 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.30.0 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Page Counters will not work correctly until rebuild is done. > We set the snapshot values, but because the queues were not marked not empty > they are not used until the rebuild is done. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4391) tests: rework AssertionLoggerHandler
[ https://issues.apache.org/jira/browse/ARTEMIS-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4391. Resolution: Fixed > tests: rework AssertionLoggerHandler > > > Key: ARTEMIS-4391 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4391 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Tests >Affects Versions: 2.30.0 >Reporter: Alexey Markevich >Priority: Major > Fix For: 2.31.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > AssertionLoggerHandler modified to be easy to use: > * no custom logger configuration required; > * implements Closeable to be poosible to use in try-with-resources statement > * split regular text check and stacktraces -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4387) Empty consumer filter string leak
[
https://issues.apache.org/jira/browse/ARTEMIS-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4387.
Resolution: Fixed
> Empty consumer filter string leak
> -
>
> Key: ARTEMIS-4387
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4387
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.26.0, 2.27.0, 2.27.1, 2.28.0, 2.29.0, 2.30.0
>Reporter: Jan Šmucr
>Priority: Major
> Labels: leak
> Fix For: 2.31.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Repeated creation and disposal of queue consumers with empty string
> ({{{}""{}}}) filters causes these strings to build up within a {{QueueInfo}}
> instance belonging to that queue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4410) Openwire prefetched messages can be out of order after failover to an exclusive queue
[ https://issues.apache.org/jira/browse/ARTEMIS-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4410. Resolution: Fixed > Openwire prefetched messages can be out of order after failover to an > exclusive queue > - > > Key: ARTEMIS-4410 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4410 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: OpenWire >Affects Versions: 2.30.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.31.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > related to ARTEMIS-4284 but when the connection drops, and the client > reconnects. Any inflight messages can be addSorted to the queue, but any new > consumer on a newly created connection can see the queue without certainty > that prefetched are added back. > with an exclusive queue, the order should be preserved for each successive > exclusive consumer. > The default prefetch means this is typical with openwire, but the visibility > of delivered messages is not unique to that protocol. With any unacked > messages that exceed credit this can occur in the event of unclean disconnect > and reconnect. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4373) Upgrade Karaf to 4.4.3
[
https://issues.apache.org/jira/browse/ARTEMIS-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4373.
Resolution: Fixed
> Upgrade Karaf to 4.4.3
> --
>
> Key: ARTEMIS-4373
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4373
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
>Affects Versions: 2.30.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> PR builds on JDK 20 (seemingly beginning with 20.0.2) recently started
> failing with:
> {noformat}
> Error: Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.3.3:verify (verify) on project
> artemis-features: Execution verify of goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.3.3:verify failed: A required
> class was missing while executing
> org.apache.karaf.tooling:karaf-maven-plugin:4.3.3:verify:
> org/apache/karaf/features/internal/download/DownloadManager{noformat}
> Moving to 4.4.3 resolves the issue. PR builds are able to finish normally.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4402) add unit tests to exercise semi-generated LogBundle code more directly
[ https://issues.apache.org/jira/browse/ARTEMIS-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4402. Resolution: Fixed > add unit tests to exercise semi-generated LogBundle code more directly > -- > > Key: ARTEMIS-4402 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4402 > Project: ActiveMQ Artemis > Issue Type: Test > Components: Tests >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.31.0 > > > Add unit tests to exercise the semi-generated LogBundle related code more > directly, showing up issues in the generation quicker/more-specifically for > given modules, rather than relying on failures that occur when running much > of the wider more general client+broker test suite (though a lot of which > aren't run in the PR test jobs). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4392) Upgrade Netty to 4.1.96.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4392. Resolution: Fixed > Upgrade Netty to 4.1.96.Final > - > > Key: ARTEMIS-4392 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4392 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Emmanuel Hugonnet >Assignee: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4376) Add Dockerfile for Alpine + JRE 11
[
https://issues.apache.org/jira/browse/ARTEMIS-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4376.
Fix Version/s: 2.31.0
Resolution: Fixed
> Add Dockerfile for Alpine + JRE 11
> --
>
> Key: ARTEMIS-4376
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4376
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This will be used along with the existing {{Dockerfile-ubuntu-11-jre}} when
> pushing images to https://hub.docker.com/r/apache/activemq-artemis.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4368) ensure predictable order of subjects for accurate logging
[ https://issues.apache.org/jira/browse/ARTEMIS-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4368. Fix Version/s: 2.31.0 (was: 2.30.0) Resolution: Fixed > ensure predictable order of subjects for accurate logging > - > > Key: ARTEMIS-4368 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4368 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: JAAS >Affects Versions: 2.29.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.31.0 > > > all our login modules that apply role and user principals need to use ordered > sets to populate the ordered sets of the subject. This ensure that the first > principal is the user principal, which is useful when we log. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4159) Support duplicate cache size configuration per address
[ https://issues.apache.org/jira/browse/ARTEMIS-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4159. Fix Version/s: 2.31.0 Resolution: Fixed > Support duplicate cache size configuration per address > -- > > Key: ARTEMIS-4159 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4159 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > As an administrator, and since each address already has its own cache-id, I > would like to be able to have a id-cache-size configured per address (which > will default to the global setting in case it doesn't exist). > Motivation: we currently have a quite large number of address, and each > address has different id-cache-size requirements. Today, to implement that, > we have to deploy several instances. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4375) JLine3 integration
[ https://issues.apache.org/jira/browse/ARTEMIS-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4375. Fix Version/s: 2.31.0 Resolution: Fixed > JLine3 integration > -- > > Key: ARTEMIS-4375 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4375 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > > Integration with jLine3 on the shell. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4418) openwire lastDeliveredSequenceId depends on message order, it should not
[ https://issues.apache.org/jira/browse/ARTEMIS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4418. Resolution: Fixed > openwire lastDeliveredSequenceId depends on message order, it should not > > > Key: ARTEMIS-4418 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4418 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: OpenWire >Affects Versions: 2.30.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.31.0 > > > Following up on ARTEMIS-4410, message order is necessary to make sense of the > openwire consumer close lastDeliveredSequence id, when order is compromised > the delivery count on prefetched messages can get incremented in error. > The root cause is the use of the persistence id, or store order, which is > itself loose. It would be better if the sequence id was directly related to > the consumer delivered list and independent of total queue order. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4355) Update to Сurator 5.5.0 and Zookeeper 3.8.2
[ https://issues.apache.org/jira/browse/ARTEMIS-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4355. Resolution: Fixed > Update to Сurator 5.5.0 and Zookeeper 3.8.2 > --- > > Key: ARTEMIS-4355 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4355 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade > Components: Clustering >Affects Versions: 2.29.0 >Reporter: Alexey Markevich >Priority: Minor > Fix For: 2.31.0 > > Time Spent: 5h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4405) Incorrect username logging in AMQ601264 events
[
https://issues.apache.org/jira/browse/ARTEMIS-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4405.
Resolution: Fixed
> Incorrect username logging in AMQ601264 events
> --
>
> Key: ARTEMIS-4405
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4405
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.30.0
>Reporter: Aleksandr Milovidov
>Assignee: Justin Bertram
>Priority: Minor
> Fix For: 2.31.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We have ActiveMQ Artemis with audit logging turned on, and sometimes wrong
> username is logged when user gets an authorization error (audit log event
> AMQ601264). I have reproduced this issue when client uses STOMP to connect to
> the broker. In that case client username is always logged as anonymous, and
> source IP address seems to be correct.
> We have a lot of other audit log messages where different usernames are
> logged in single log event, but I cannot attach these logs because it
> contains sensitive information. I think this problem is not specific to STOMP
> clients because most our clients use core and openwire. I will try to
> reproduce it later.
> The problem is not specific to the current version of Artemis.
> Steps to reproduce (for STOMP client):
> 1. Create Artemis instance
> {{artemis create --user admin --password admin --require-login }}
> Edit {{artemis-roles.properties}} and {{artemis-users.properties}} to create
> some other user with password and non-admin role. For example, add string
> {{alice = alice}} to both files.
> Edit log4j2.properties to enable base audit logging:
> {code:java}
> logger.audit_base = INFO, audit_log_file{code}
> To connect to the broker with STOMP I have used python with Stompest library
> (it has to be installed using pip install stompest).
> Example STOMP producer python code (it does not handle authorization errors):
>
> {code:java}
> from stompest.config import StompConfig
> from stompest.protocol import StompSpec
> from stompest.sync import Stomp
> CONFIG = StompConfig("tcp://localhost:61613", login="alice",
> passcode="alice", version=StompSpec.VERSION_1_0)
> QUEUE = 'test.queue'
> client = Stomp(CONFIG)
> client.connect()
> client.send(QUEUE, 'Test message'.encode())
> client.disconnect()
> {code}
> Run this example code. Check broker audit.log. For example:
>
> {code:java}
> 2023-08-28 17:39:20,042 [AUDIT](Thread-1 (activemq-netty-threads)) AMQ601267:
> User alice(alice)@127.0.0.1:56685 is creating a core session on target
> resource ActiveMQServerImpl::name=0.0.0.0 with parameters:
> [ac22db0e-45b0-11ee-b333-005056abe8b9, alice, , 102400,
> org.apache.activemq.artemis.core.protocol.stomp.StompConnection@3313e538,
> true, false, false, false, null,
> org.apache.activemq.artemis.core.protocol.stomp.StompSession@2fc820ee, true,
> {}]
> 2023-08-28 17:39:20,081 [AUDIT](Thread-1 (activemq-netty-threads)) AMQ601262:
> User alice(alice)@127.0.0.1:56685 is creating address on target resource:
> ac22db0e-45b0-11ee-b333-005056abe8b9 with parameters: [Address
> [name=test.queue, id=0, routingTypes={MULTICAST}, autoCreated=false,
> paused=false, bindingRemovedTimestamp=-1, swept=false,
> createdTimestamp=1693233560081], true]
> 2023-08-28 17:39:20,116 [AUDIT](Thread-1 (activemq-netty-threads)) AMQ601264:
> User anonymous@127.0.0.1:56685 gets security check failure, reason =
> AMQ229032: User: alice does not have permission='CREATE_ADDRESS' on address
> test.queue
> org.apache.activemq.artemis.api.core.ActiveMQSecurityException: AMQ229032:
> User: alice does not have permission='CREATE_ADDRESS' on address test.queue
> at
> org.apache.activemq.artemis.core.security.impl.SecurityStoreImpl.check(SecurityStoreImpl.java:305)
> [artemis-server-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.security.impl.SecurityStoreImpl.check(SecurityStoreImpl.java:227)
> [artemis-server-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.securityCheck(ServerSessionImpl.java:503)
> [artemis-server-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.createAddress(ServerSessionImpl.java:972)
> [artemis-server-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.createAddress(ServerSessionImpl.java:962)
> [artemis-server-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.protocol.stomp.StompConnection.autoCreateDestinationIfPossible(StompConnection.java:184)
> [artemis-stomp-protocol-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.protocol.stomp.VersionedStompFrameHandler.onSend(VersionedStompFrameHandler.java:188)
> [artemis-stomp-protocol-2.30.0.j
[jira] [Closed] (ARTEMIS-4424) "AMQ212025: did not connect the cluster" when bootstrapping a static cluster
[ https://issues.apache.org/jira/browse/ARTEMIS-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4424. Resolution: Fixed > "AMQ212025: did not connect the cluster" when bootstrapping a static cluster > > > Key: ARTEMIS-4424 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4424 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Say you are bootstrapping a cluster. The first node will have static > connectors to the other nodes, and you will see this quite repetitively in > the logs: > [main] 09:56:58,606 WARN [org.apache.activemq.artemis.core.client] > AMQ212025: did not connect the cluster connection to other nodes > java.lang.Exception: null > at > org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.(ServerLocatorImpl.java:326) > ~[classes/:?] > at > org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.(ServerLocatorImpl.java:378) > [classes/:?] > at > org.apache.activemq.artemis.api.core.client.ActiveMQClient.createServerLocatorWithoutHA(ActiveMQClient.java:311) > ~[classes/:?] > at > org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:51) > ~[classes/:?] > at > org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:33) > ~[classes/:?] > at > org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:84) > ~[classes/:?] > at > org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:28) > ~[classes/:?] > at > org.apache.activemq.artemis.utils.uri.URIFactory.newObject(URIFactory.java:59) > ~[classes/:?] > This is because the connect method will log.warn when no nodes are connected, > and throw an exception. > There's no need for the logger.warn in this situation as the caller will be > responsible for the retry loop. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4397) Problem with bootstrap.xml after artemis upgrade
[
https://issues.apache.org/jira/browse/ARTEMIS-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4397.
Fix Version/s: 2.31.0
Resolution: Fixed
> Problem with bootstrap.xml after artemis upgrade
> -
>
> Key: ARTEMIS-4397
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4397
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.29.0, 2.30.0
>Reporter: Aleksandr Milovidov
>Assignee: Clebert Suconic
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> We have found strange problem when upgrading ActiveMQ Artemis instance from
> version 2.29.0 and higher to the same or higher version.
> After running command {{{}artemis upgrade /path/to/instance{}}}, web section
> in bootstrap.xml is broken and Artemis cannot start. It looks like:
> {code:java}
>
>http://localhost:8161";>
>war="activemq-branding.war"/>
>war="artemis-plugin.war"/>
>
>
> {code}
> After each upgrade, duplicate property "name" is added to the some app
> sections.
> When upgrading to the current version, it also breaks bootstrap.xml. Tried in
> Windows and Linux, does not differ.
> When upgrading from 2.28 and earlier, it does not cause problem. I'm not sure
> but it seems that bootstrap.xml does not contain name property in previous
> versions.
> Steps to reproduce: unzip apache-artemis archive, create instance and upgrade
> (Windows example):
> {{artemis.cmd create --user admin --password password --require-login
> C:\path\to\artemis-inst-2.29.0}}
> {{artemis.cmd upgrade C:\path\to\artemis-inst-2.29.0}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4398) Support configuring Database with Broker Properties
[ https://issues.apache.org/jira/browse/ARTEMIS-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4398. Fix Version/s: 2.31.0 Resolution: Fixed > Support configuring Database with Broker Properties > --- > > Key: ARTEMIS-4398 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4398 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.31.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4386) consolidate used servlet-api deps
[ https://issues.apache.org/jira/browse/ARTEMIS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4386. Resolution: Fixed > consolidate used servlet-api deps > - > > Key: ARTEMIS-4386 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4386 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.31.0 > > > The build is currently using multiple servlet API deps, and the broker > assembly archive even includes a couple. They can be consolidated on one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
[ https://issues.apache.org/jira/browse/ARTEMIS-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4431. Resolution: Fixed > AMQP federated address consumer not applying hops annotation correctly > -- > > Key: ARTEMIS-4431 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The AMQP federation address consumer omits a call to re-encode the message > after updating the hops annotation that track how many federation links the > message has traversed. This results in the message not carrying forward the > correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4385) Expand queue stat to other members of the topology
[ https://issues.apache.org/jira/browse/ARTEMIS-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4385. Fix Version/s: 2.31.0 Resolution: Fixed > Expand queue stat to other members of the topology > -- > > Key: ARTEMIS-4385 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4385 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.31.0 > > > I thought about doing this by default but the visualization would be > overwhelming. > if you did ./artemis queue stat --clustered > all the members of the topology would be shown on queue stats. > I'm also adding a quick note about --clustered if the node is clustered. > this is because this would help to visualize what happened to messages if > redistribution is not happening or someting like that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4399) Authentication cache set to size 0 (i.e. disabled) is not threadsafe
[
https://issues.apache.org/jira/browse/ARTEMIS-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4399.
Resolution: Fixed
> Authentication cache set to size 0 (i.e. disabled) is not threadsafe
> -
>
> Key: ARTEMIS-4399
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4399
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.30.0
>Reporter: Rich T
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> To disable authentication cache you have to set the following config option:
> {code:java}
> setAuthenticationCacheSize(0){code}
> SecurityStoreImpl then creates the following guava cache with maximumSize set
> to 0:
> {code:java}
> authenticationCache = CacheBuilder.newBuilder()
> .maximumSize(authenticationCacheSize)
> .expireAfterWrite(invalidationInterval, TimeUnit.MILLISECONDS)
> .build();{code}
> The way the guava LocalCache implementation works with maximumSize is that
> even with size 0 an entry is added but then is removed; this means that
> another thread can end up pulling an entry out of the cache before it is
> evicted; even though maximumSize is set to 0.
> It has taken me some effort to track down this timing issue but the behaviour
> is also explained in the guava docs:
> {code:java}
> When size is zero, elements will be evicted immediately after being loaded
> into the cache. This can be useful in testing, or to disable caching
> temporarily without a code change.This feature cannot be used in conjunction
> with maximumWeight
> {code}
> Based on these findings no auth cache should be created at all when size 0 is
> requested.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4417) AbstractJournalStorageManager storeKeyValuePair + deleteKeyValuePair are not thread safe
[ https://issues.apache.org/jira/browse/ARTEMIS-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4417. Resolution: Fixed > AbstractJournalStorageManager storeKeyValuePair + deleteKeyValuePair are not > thread safe > > > Key: ARTEMIS-4417 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4417 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Balancer >Affects Versions: 2.30.0 >Reporter: Robbie Gemmell >Priority: Major > Fix For: 2.31.0 > > > Continuing on from ARTEMIS-4406, the calls to AbstractJournalStorageManager > storeKeyValuePair + deleteKeyValuePair used by LocalCache as part of the > connection-router implementation are themselves also not entirely thread safe. > A ConcurrentHashMap is used for the initial structure, however a regular > HashMap sub-map is then stored within the concurrent outer map, which can > then also be accessed concurrently, meaning the methods aren't currently > thread safe; it also needs to be a ConcurrentHashMap. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4413) CheckTest.testNodeCheckTopology fails sporadically
[ https://issues.apache.org/jira/browse/ARTEMIS-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4413. Fix Version/s: 2.31.0 Resolution: Fixed > CheckTest.testNodeCheckTopology fails sporadically > -- > > Key: ARTEMIS-4413 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4413 > Project: ActiveMQ Artemis > Issue Type: Test >Affects Versions: 2.31.0 >Reporter: Robbie Gemmell >Priority: Major > Fix For: 2.31.0 > > Time Spent: 10m > Remaining Estimate: 0h > > CheckTest.testNodeCheckTopology fails sporadically in CI, due to a thread > leak from shutdown issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4394) management console war file contains some duplicate jars
[ https://issues.apache.org/jira/browse/ARTEMIS-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4394. Resolution: Fixed > management console war file contains some duplicate jars > > > Key: ARTEMIS-4394 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4394 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.30.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.31.0 > > > The management console.war file contains some 'duplicate' lib jars due to the > way the console module build works. As part of its creation it repackages the > hawtio war, removing some logging deps + config the broker supplies, and also > updating the contained guava version to match the current managed version > used elsewhere in the codebase. For the latter process, some transitive > dependencies are being duplicated with both the original and updated versions > then being present in the new war. As these are mainly build time related > annotation dependencies, which we actually exclude elsewhere in the build, it > is likely not problematic; however it still shouldn't be the case. Update the > process to exclude the originals and so use only the newer replacement > version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4390) Windows build fails smoke tests on upgrade-linux
[
https://issues.apache.org/jira/browse/ARTEMIS-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4390.
Resolution: Fixed
> Windows build fails smoke tests on upgrade-linux
>
>
> Key: ARTEMIS-4390
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4390
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Tests
> Environment: Windows 10 Enterprise b19045
> Java 11 (Temurin-11.0.15+10)
>Reporter: Jan Šmucr
>Priority: Major
> Fix For: 2.31.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The {{upgrade-linux}} test doesn't pass on Windows, as it wrongly assumes
> Linux-like environment, and therefore it cannot find the {{artemis.cmd}}
> script to fiddle with.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4404) Update the artemis-docker readme.md with minor clarification on building local distribution
[ https://issues.apache.org/jira/browse/ARTEMIS-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4404. Fix Version/s: 2.31.0 Resolution: Fixed > Update the artemis-docker readme.md with minor clarification on building > local distribution > --- > > Key: ARTEMIS-4404 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4404 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.30.0 >Reporter: Mike Williams >Priority: Trivial > Labels: documentation > Fix For: 2.31.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > I recently tried to build my own docker image from source following the > readme in artemis-docker. Ran into some difficulty, mostly because I was a > newbie on the project I think. However, I feel the documentation could have > been slightly clearer and I'm proposing some minor changes to the readme file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4374) Upgrade Pax Exam to 4.13.5
[ https://issues.apache.org/jira/browse/ARTEMIS-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4374. Resolution: Fixed > Upgrade Pax Exam to 4.13.5 > -- > > Key: ARTEMIS-4374 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4374 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade > Components: osgi >Affects Versions: 2.29.0 >Reporter: Alexey Markevich >Priority: Minor > Fix For: 2.31.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4423) Upgrade Netty to 4.1.97.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4423. Resolution: Fixed > Upgrade Netty to 4.1.97.Final > - > > Key: ARTEMIS-4423 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4423 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Emmanuel Hugonnet >Assignee: Justin Bertram >Priority: Major > Fix For: 2.31.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4412) openwire TwoBrokerFailoverClusterTest test fails sporadically
[ https://issues.apache.org/jira/browse/ARTEMIS-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4412. Resolution: Fixed > openwire TwoBrokerFailoverClusterTest test fails sporadically > - > > Key: ARTEMIS-4412 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4412 > Project: ActiveMQ Artemis > Issue Type: Test > Components: Tests >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.31.0 > > > The openwire TwoBrokerFailoverClusterTest test fails sporadically. It is > balancing 30 connections between 2 brokers with randomized connect, and fails > if <35% hit one node. I've only seen it fail because 33.33% hit one node, i.e > the difference between 10 and 11 connections. It doesnt seem that anything in > play ensures >= 35% actually end up on one node, and the test is just making > a slightly optimistic take on what randomizing between 2 things could do. > Make it a bit less optimistic to help cut out the sporadic failures while > still validating there is a spread. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
[ https://issues.apache.org/jira/browse/ARTEMIS-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-4431: - Fix Version/s: 2.31.0 (was: 2.32.0) > AMQP federated address consumer not applying hops annotation correctly > -- > > Key: ARTEMIS-4431 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The AMQP federation address consumer omits a call to re-encode the message > after updating the hops annotation that track how many federation links the > message has traversed. This results in the message not carrying forward the > correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
[ https://issues.apache.org/jira/browse/ARTEMIS-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4431. Resolution: Fixed > AMQP federated address consumer not applying hops annotation correctly > -- > > Key: ARTEMIS-4431 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.31.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The AMQP federation address consumer omits a call to re-encode the message > after updating the hops annotation that track how many federation links the > message has traversed. This results in the message not carrying forward the > correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (AMQ-8464) Implement JMS 2.0 Consumer receiveBody
[ https://issues.apache.org/jira/browse/AMQ-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-8464 started by Matt Pavlovich. --- > Implement JMS 2.0 Consumer receiveBody > -- > > Key: AMQ-8464 > URL: https://issues.apache.org/jira/browse/AMQ-8464 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Labels: #jms2 > Fix For: 6.0.0, 5.18.3 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
[ https://issues.apache.org/jira/browse/ARTEMIS-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765704#comment-17765704 ] ASF subversion and git services commented on ARTEMIS-4431: -- Commit e8d92b3bc59f12d44ba46a45562f64f6a9fb4ff6 in activemq-artemis's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e8d92b3bc5 ] ARTEMIS-4431 Re-encode the AMQP message annotations if hops are updates When updating or adding the hops value the AMQP message needs a re-encode to carry that value forward when the message is sent to the next broker. > AMQP federated address consumer not applying hops annotation correctly > -- > > Key: ARTEMIS-4431 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The AMQP federation address consumer omits a call to re-encode the message > after updating the hops annotation that track how many federation links the > message has traversed. This results in the message not carrying forward the > correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
[ https://issues.apache.org/jira/browse/ARTEMIS-4431?focusedWorklogId=880698&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-880698 ] ASF GitHub Bot logged work on ARTEMIS-4431: --- Author: ASF GitHub Bot Created on: 15/Sep/23 15:41 Start Date: 15/Sep/23 15:41 Worklog Time Spent: 10m Work Description: gemmellr merged PR #4618: URL: https://github.com/apache/activemq-artemis/pull/4618 Issue Time Tracking --- Worklog Id: (was: 880698) Time Spent: 20m (was: 10m) > AMQP federated address consumer not applying hops annotation correctly > -- > > Key: ARTEMIS-4431 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The AMQP federation address consumer omits a call to re-encode the message > after updating the hops annotation that track how many federation links the > message has traversed. This results in the message not carrying forward the > correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
[ https://issues.apache.org/jira/browse/ARTEMIS-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4431: Fix Version/s: 2.32.0 (was: 2.31.0) Affects Version/s: 2.31.0 (was: 2.30.0) > AMQP federated address consumer not applying hops annotation correctly > -- > > Key: ARTEMIS-4431 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.31.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.32.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The AMQP federation address consumer omits a call to re-encode the message > after updating the hops annotation that track how many federation links the > message has traversed. This results in the message not carrying forward the > correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
[ https://issues.apache.org/jira/browse/ARTEMIS-4431?focusedWorklogId=880694&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-880694 ] ASF GitHub Bot logged work on ARTEMIS-4431: --- Author: ASF GitHub Bot Created on: 15/Sep/23 15:11 Start Date: 15/Sep/23 15:11 Worklog Time Spent: 10m Work Description: tabish121 opened a new pull request, #4618: URL: https://github.com/apache/activemq-artemis/pull/4618 When updating or adding the hops value the AMQP message needs a re-encode to carry that value forward when the message is sent to the next broker. Issue Time Tracking --- Worklog Id: (was: 880694) Remaining Estimate: 0h Time Spent: 10m > AMQP federated address consumer not applying hops annotation correctly > -- > > Key: ARTEMIS-4431 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.30.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.31.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The AMQP federation address consumer omits a call to re-encode the message > after updating the hops annotation that track how many federation links the > message has traversed. This results in the message not carrying forward the > correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4431) AMQP federated address consumer not applying hops annotation correctly
Timothy A. Bish created ARTEMIS-4431: Summary: AMQP federated address consumer not applying hops annotation correctly Key: ARTEMIS-4431 URL: https://issues.apache.org/jira/browse/ARTEMIS-4431 Project: ActiveMQ Artemis Issue Type: Bug Components: AMQP Affects Versions: 2.30.0 Reporter: Timothy A. Bish Assignee: Timothy A. Bish Fix For: 2.31.0 The AMQP federation address consumer omits a call to re-encode the message after updating the hops annotation that track how many federation links the message has traversed. This results in the message not carrying forward the correct annotation which breaks the max hops configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-8324) Implement JMS 2.0 MessageProducer CompletionListener methods
[ https://issues.apache.org/jira/browse/AMQ-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-8324: -- Fix Version/s: 5.19.0 (was: 5.20.0) > Implement JMS 2.0 MessageProducer CompletionListener methods > > > Key: AMQ-8324 > URL: https://issues.apache.org/jira/browse/AMQ-8324 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Labels: #jms2 > Fix For: 5.19.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > CompletionListener, etc -- This message was sent by Atlassian Jira (v8.20.10#820010)
