[jira] [Commented] (ARTEMIS-4731) Openwire failure detection leak with Windows Clients / Server won't cleanup openwork clients with Exception
[ https://issues.apache.org/jira/browse/ARTEMIS-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838855#comment-17838855 ] ASF subversion and git services commented on ARTEMIS-4731: -- Commit 6fe53b813a0e958b73ea3e703bad7b0c892e6044 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6fe53b813a ] ARTEMIS-4731 OpenWireConnection exception listener should call transport.close(); this is causing a leak for server objects > Openwire failure detection leak with Windows Clients / Server won't cleanup > openwork clients with Exception > --- > > Key: ARTEMIS-4731 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4731 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.33.0 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The OpenWireServerConnection won't deal properly with Exceptions raised by > Netty. > Windows clients will send a different signal to the server causing the > connection to throw an exception rather than issue a disconnect, > As a result some objects are being left on the heap as transport.close() is > not being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4723) org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal
[ https://issues.apache.org/jira/browse/ARTEMIS-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838770#comment-17838770 ] ASF subversion and git services commented on ARTEMIS-4723: -- Commit 69f68691574bb2d5f9c5b8f3fcf6ec4f1b0dc59d in activemq-artemis's branch refs/heads/openwire-fix from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=69f6869157 ] ARTEMIS-4723 Optimization on HandlerBase No need to create a new instance every time the processor starts executing. The instance of counter can be reused and stored in the Thread. > org.apache.activemq.artemis.utils.actors.Handler$Counter left on the > ThreadLocal > > > Key: ARTEMIS-4723 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4723 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.34.0 > > Time Spent: 1h > Remaining Estimate: 0h > > org.apache.activemq.artemis.utils.actors.Handler$Counter is left on the > ThreadLocal. > This is used to verify if the execution is InHander. > The object could be removed after done. So it's not a growing leak (meaning > it will keep growing), but it's an unnecessary allocation that can be avoided. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838598#comment-17838598 ] ASF subversion and git services commented on ARTEMIS-1921: -- Commit 791630fa861f868beb3e2d778eb44f92117b0220 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=791630fa86 ] ARTEMIS-1921 setting client ID on core JMS should be reflected in broker RemotingConnection > Setting client ID on core JMS should be reflected in broker RemotingConnection > -- > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Assignee: Justin Bertram >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > Time Spent: 20m > Remaining Estimate: 0h > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4723) org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal
[ https://issues.apache.org/jira/browse/ARTEMIS-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838403#comment-17838403 ] ASF subversion and git services commented on ARTEMIS-4723: -- Commit 31243b10239184602a30749be8d83091e1e68c34 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=31243b1023 ] ARTEMIS-4723 Optimization on HandlerBase No need to create a new instance every time the processor starts executing. The instance of counter can be reused and stored in the Thread. > org.apache.activemq.artemis.utils.actors.Handler$Counter left on the > ThreadLocal > > > Key: ARTEMIS-4723 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4723 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.34.0 > > Time Spent: 1h > Remaining Estimate: 0h > > org.apache.activemq.artemis.utils.actors.Handler$Counter is left on the > ThreadLocal. > This is used to verify if the execution is InHander. > The object could be removed after done. So it's not a growing leak (meaning > it will keep growing), but it's an unnecessary allocation that can be avoided. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4723) org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal
[ https://issues.apache.org/jira/browse/ARTEMIS-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838344#comment-17838344 ] ASF subversion and git services commented on ARTEMIS-4723: -- Commit e4a6687cd46421cf4fc89c3fa941f439772b6d29 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e4a6687cd4 ] ARTEMIS-4723 Avoid objects left on ThreadLocal from OrderedExecutorFactory co-authored: Jakob van Kruijssen > org.apache.activemq.artemis.utils.actors.Handler$Counter left on the > ThreadLocal > > > Key: ARTEMIS-4723 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4723 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > org.apache.activemq.artemis.utils.actors.Handler$Counter is left on the > ThreadLocal. > This is used to verify if the execution is InHander. > The object could be removed after done. So it's not a growing leak (meaning > it will keep growing), but it's an unnecessary allocation that can be avoided. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4729) Upgrade slf4j version to 2.0.12
[ https://issues.apache.org/jira/browse/ARTEMIS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838001#comment-17838001 ] ASF subversion and git services commented on ARTEMIS-4729: -- Commit f4581deb9dfa665b8a28c3f027ff7c71defca630 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=f4581deb9d ] ARTEMIS-4729 Upgrade slf4j version to 2.0.12 > Upgrade slf4j version to 2.0.12 > --- > > Key: ARTEMIS-4729 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4729 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4728) Upgrade jgroups version to 5.3.4.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838000#comment-17838000 ] ASF subversion and git services commented on ARTEMIS-4728: -- Commit e065b4448fd03d573b34973044ba654b9212246b in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e065b4448f ] ARTEMIS-4728 Upgrade jgroups version to 5.3.4.Final > Upgrade jgroups version to 5.3.4.Final > -- > > Key: ARTEMIS-4728 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4728 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4725) Mirror may send wrong headers
[ https://issues.apache.org/jira/browse/ARTEMIS-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837926#comment-17837926 ] ASF subversion and git services commented on ARTEMIS-4725: -- Commit 8880ae92d9e3c3160bcc66e0028d29972db326ba in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=8880ae92d9 ] ARTEMIS-4725 Fixing intermittent failure on test > Mirror may send wrong headers > - > > Key: ARTEMIS-4725 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4725 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Time Spent: 3h 50m > Remaining Estimate: 0h > > This is not specifically an issue in Mirroring or Broker Connection, but it > manifested as part of the broker connection codebase. > When a delivery for the first time after a reload happens, the delivery > annotation may be written before the header, breaking the specification. > Later on delivery the message, createDelieryCopy could get confused with the > positions: > https://github.com/apache/activemq-artemis/blob/50fae08b09a76e200ef107d06cc867231f644ccd/artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java#L829 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4725) Mirror may send wrong headers
[ https://issues.apache.org/jira/browse/ARTEMIS-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837837#comment-17837837 ] ASF subversion and git services commented on ARTEMIS-4725: -- Commit 329d963717d5e73e22d181e251fae20fc5c73809 in activemq-artemis's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=329d963717 ] ARTEMIS-4725 Fix AMQP outgoing encoding if da encoded before header Fix the AMQP message scanning to account for the header not being at the front of the buffer which also accounts for odd case of broker storing message with delivery annotations ahead of the header. > Mirror may send wrong headers > - > > Key: ARTEMIS-4725 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4725 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Time Spent: 3h 50m > Remaining Estimate: 0h > > This is not specifically an issue in Mirroring or Broker Connection, but it > manifested as part of the broker connection codebase. > When a delivery for the first time after a reload happens, the delivery > annotation may be written before the header, breaking the specification. > Later on delivery the message, createDelieryCopy could get confused with the > positions: > https://github.com/apache/activemq-artemis/blob/50fae08b09a76e200ef107d06cc867231f644ccd/artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java#L829 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4725) Mirror may send wrong headers
[ https://issues.apache.org/jira/browse/ARTEMIS-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837838#comment-17837838 ] ASF subversion and git services commented on ARTEMIS-4725: -- Commit eb7b0b09467c0395dbb5d628ccb93734feae1f5e in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=eb7b0b0946 ] ARTEMIS-4725 Mirroring tests using multiple versions > Mirror may send wrong headers > - > > Key: ARTEMIS-4725 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4725 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Time Spent: 3h 50m > Remaining Estimate: 0h > > This is not specifically an issue in Mirroring or Broker Connection, but it > manifested as part of the broker connection codebase. > When a delivery for the first time after a reload happens, the delivery > annotation may be written before the header, breaking the specification. > Later on delivery the message, createDelieryCopy could get confused with the > positions: > https://github.com/apache/activemq-artemis/blob/50fae08b09a76e200ef107d06cc867231f644ccd/artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java#L829 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4625) Upgrade CheckStyle to 10.15.0
[ https://issues.apache.org/jira/browse/ARTEMIS-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837650#comment-17837650 ] ASF subversion and git services commented on ARTEMIS-4625: -- Commit 7072eb187ac4dea1a68414823e7b883a38ee319a in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7072eb187a ] ARTEMIS-4625 upgrade CheckStyle to 10.15.0 > Upgrade CheckStyle to 10.15.0 > - > > Key: ARTEMIS-4625 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4625 > 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-1691) JMS Bridge: After the FailureHandler exits, a bridge cannot be started full functional anymore
[
https://issues.apache.org/jira/browse/ARTEMIS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837504#comment-17837504
]
ASF subversion and git services commented on ARTEMIS-1691:
--
Commit a1db72395c055069439870ca147ebde6a0d16f44 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=a1db72395c ]
ARTEMIS-1691 JMS bridge can't be manually restarted after failure
> JMS Bridge: After the FailureHandler exits, a bridge cannot be started full
> functional anymore
> --
>
> Key: ARTEMIS-1691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.4.0
> Environment: WildFly Servers.
>Reporter: Markus F
>Assignee: Justin Bertram
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h4. Setup
> JMSBridge on server a pulls messages from a remote server B.
> failureRetryInterval = 1 sec
> maxRetries = 1
> h4. To Reproduce
> Restart the remote server (need to take more than one second.)
> JMS Bridge prints out:
> {noformat}
> JMS Bridge unable to set up connections, bridge will be stopped{noformat}
> After the remote server is up again, start the bridge again.
> JMS Bridge prints out:
> {noformat}
> Started JMS Bridge testbridge{noformat}
> h4. Result:
> The bridge is started, but does still not consume messages.
> h4. Reason
> In {{JMSBridgeImpl}} line 1624, the failed boolean parameter is checked. It
> is not set to true anywhere outside the failure handlers ({{FailureHandler}}
> and {{StartupFailureHandler}}) or on initial adding of the bridge.
> But the {{FailureHandler}} has already exited. So the bridge will wait all
> time long for 500 ms in line 1626.
> h4. Solution
> I would add a
> {code:java}
> failed = false;{code}
> after line 403.
> I don't know how the release process is handled here, if I can make a pull
> request or something like that, I will do, if it is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4724) Upgrade karaf version to 4.4.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837263#comment-17837263 ] ASF subversion and git services commented on ARTEMIS-4724: -- Commit 021993fe7ccbd39936c2b6450a7e9d9a551ed9e2 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=021993fe7c ] ARTEMIS-4724 Upgrade karaf version to 4.4.6 > Upgrade karaf version to 4.4.6 > -- > > Key: ARTEMIS-4724 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4724 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4582) add view and edit permissions to extend security-settings rbac for management operations
[ https://issues.apache.org/jira/browse/ARTEMIS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837241#comment-17837241 ] ASF subversion and git services commented on ARTEMIS-4582: -- Commit 66caefe1d7309cf453f98dd1d048ebe0a3aaef28 in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=66caefe1d7 ] ARTEMIS-4582 - fix missed change from update to view naming in the doc > add view and edit permissions to extend security-settings rbac for management > operations > > > Key: ARTEMIS-4582 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4582 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker, Configuration, JMX, Web Console >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.33.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > we have the manage permission that allows sending to the management address, > to access any control resource. We don't however distinguish what a user can > do. > We should segment control operations into categories: CRUD provides a basis > view for get/is (Read) > edit for set or operations that mutate or modify. > We allow this sort of configuration via management.xml for jmx mbean access > but using a different model based on object name. > All of the mbeans delegate to the control resources. > If we add these two additional permissions then we can have a single rbac > model (that supports config reload) and more granularity on control resource > access from the management address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4582) add view and edit permissions to extend security-settings rbac for management operations
[ https://issues.apache.org/jira/browse/ARTEMIS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837231#comment-17837231 ] ASF subversion and git services commented on ARTEMIS-4582: -- Commit e43707aba953c4edc33e9370fa89526a5337e3f0 in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e43707aba9 ] ARTEMIS-4582 - doc update to remove incorrect info > add view and edit permissions to extend security-settings rbac for management > operations > > > Key: ARTEMIS-4582 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4582 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker, Configuration, JMX, Web Console >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.33.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > we have the manage permission that allows sending to the management address, > to access any control resource. We don't however distinguish what a user can > do. > We should segment control operations into categories: CRUD provides a basis > view for get/is (Read) > edit for set or operations that mutate or modify. > We allow this sort of configuration via management.xml for jmx mbean access > but using a different model based on object name. > All of the mbeans delegate to the control resources. > If we add these two additional permissions then we can have a single rbac > model (that supports config reload) and more granularity on control resource > access from the management address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1729) Automatically check for broken documentation links
[
https://issues.apache.org/jira/browse/ARTEMIS-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836745#comment-17836745
]
ASF subversion and git services commented on ARTEMIS-1729:
--
Commit 66fcd7f4cf554a833d0fe3ee7760d2e083e01fca in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=66fcd7f4cf ]
ARTEMIS-1729 automatically check for broken documentation links
> Automatically check for broken documentation links
> --
>
> Key: ARTEMIS-1729
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1729
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Documentation
>Reporter: Lionel Cons
>Assignee: Justin Bertram
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Artemis GitBook documentation sometimes contains broken (internal) links.
> See for instance ARTEMIS-1076 or ARTEMIS-1721.
> It would be good to automatically check for broken links as part of the Maven
> {{test}} task.
> One way to do this would be to have a Maven task to run a webserver serving
> the generated documentation (Python can trivially do it with '{{python -m
> SimpleHTTPServer 8000}}' but an equivalent Java-based solution is probably
> better) and then a crawler checking for broken links ({{wget}} can easily be
> used for this as described in ARTEMIS-1076 but here again a Java-based
> solution is maybe better).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1551) Conversion of most of the properties is not working when crossing protocols.
[
https://issues.apache.org/jira/browse/ARTEMIS-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836696#comment-17836696
]
ASF subversion and git services commented on ARTEMIS-1551:
--
Commit f64e37622e3216be77d409b6327990f8fe4a7b00 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=f64e37622e ]
ARTEMIS-1551 validate properties between JMS clients
> Conversion of most of the properties is not working when crossing protocols.
>
>
> Key: ARTEMIS-1551
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1551
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, OpenWire
>Affects Versions: 2.3.0, 2.4.0
> Environment: Artemis 2.3.0
>Reporter: Saurabh Rai
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Send a message using Openwire client
> Receive a message using AMQP client.
> Observe most of the fields like 'group-id', 'group-sequence',
> 'reply-to-group-id' are not getting converted properly.
> {code:java}
> $ java -jar aoc-downstream-ga-5.11.0.redhat-630187.jar sender --timeout 5000
> --log-msgs dict --broker tcp://localhost:61616 --address saurabhTest --count
> 1 --conn-username admin --conn-password admin --msg-user-id tester
> --msg-group-id g1 --msg-group-seq 10 --msg-content-type application/text
> --msg-reply-to-group-id g1
> {'durable': True, 'priority': 4, 'ttl': 0, 'first-acquirer': False,
> 'delivery-count': 0, 'redelivered': False, 'id':
> 'ID:sarai.pnq.csb-44142-1512964029323-1:1:1:1:1', 'user_id':'tester',
> 'address': 'queue://saurabhTest', 'subject': None, 'reply_to': None,
> 'correlation_id': None, 'content_type': 'application/text',
> 'content_encoding': None, 'absolute-expiry-time': 0, 'creation-time':
> 1512964029569, 'group-id': 'g1', 'group-sequence': 10, 'reply-to-group-id':
> 'g1', 'properties': {'JMS_AMQP_ContentType': 'application/text',
> 'JMS_AMQP_ReplyToGroupID': 'g1', 'JMSXUserID': 'tester', 'JMSXGroupSequence':
> '10', 'JMSXGroupID': 'g1', 'JMSXGroupSeq': 0}, 'content': None, 'type': None}
> {code}
> {code:java}
> $ java -jar aac-staging-0.21.0.redhat-1.jar receiver --timeout 5 --log-msgs
> dict --broker localhost:5672 --address saurabhTest --count 1 --conn-username
> admin --conn-password admin
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x00\x01\x00\x0aJMSXUserID\x09\x00\x06tester
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x005n\x02\xae\x02{\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01\x00\x01
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x001{\x01+\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01
> {'durable': True, 'priority': 4, 'ttl': 0, 'first-acquirer': False,
> 'delivery-count': 0, 'redelivered': False, 'id': None, 'user_id': 'tester',
> 'address': 'saurabhTest', 'subject': None, 'reply_to': None,
> 'correlation_id': None, 'content_type': None, 'content_encoding': None,
> 'absolute-expiry-time': 0, 'creation-time': 1512712172006, 'group-id': None,
> 'group-sequence': 0, 'reply-to-group-id': None, 'properties':
> {'__HDR_COMMAND_ID': 5, 'JMSXDeliveryCount': 1, '__HDR_ARRIVAL': 0,
> '__HDR_GROUP_ID': 'g1', 'JMSXUserID': 'tester', '__HDR_MARSHALL_PROP':
> \x00\x00\x00\x01\x00\x0aJMSXUserID\x09\x00\x06tester, '__HDR_MESSAGE_ID':
> \x00\x00\x005n\x02\xae\x02{\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01\x00\x01,
> '__HDR_GROUP_SEQUENCE': 0, '__HDR_PRODUCER_ID':
> \x00\x00\x001{\x01+\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01,
> '__HDR_DROPPABLE': False, '__HDR_BROKER_IN_TIME': 1512712172007}, 'content':
> None}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-2492) [Doc] Confusing/old paragraph in clusters.md
[
https://issues.apache.org/jira/browse/ARTEMIS-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836417#comment-17836417
]
ASF subversion and git services commented on ARTEMIS-2492:
--
Commit aff360c70ee48bfde106d55d30858156da2b9523 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=aff360c70e ]
ARTEMIS-2492 remove defuct doc snippet
> [Doc] Confusing/old paragraph in clusters.md
>
>
> Key: ARTEMIS-2492
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2492
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Laurent Bigonville
>Assignee: Justin Bertram
>Priority: Trivial
>
> Hello
> On line 372 in clusters.md the documentation is saying:
>
> {noformat}
> The element `discovery-group-ref` specifies the name of a discovery
> group defined in `broker.xml`.{noformat}
> But there is no such _discovery-group-ref_ element in the example above.
> Is that some left over?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836287#comment-17836287 ] ASF subversion and git services commented on AMQ-9430: -- Commit abcc0dcde388fc62a063aa8a32e8432bd0a143fc in activemq's branch refs/heads/activemq-5.18.x from Matt Pavlovich [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=abcc0dcde ] [AMQ-9430] RuntimeConfigPlugin wire in classloader to JAXBContext (cherry picked from commit 1e314d8dfc0242e56762954f5397a5299eb2a36e) > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836268#comment-17836268 ] ASF subversion and git services commented on AMQ-9430: -- Commit 1e314d8dfc0242e56762954f5397a5299eb2a36e in activemq's branch refs/heads/main from Matt Pavlovich [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=1e314d8df ] [AMQ-9430] RuntimeConfigPlugin wire in classloader to JAXBContext > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > # extract amq package to linux host > tar xvf
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836269#comment-17836269 ] ASF subversion and git services commented on AMQ-9430: -- Commit f6d067a49aa0f7aea18afa7738d60f9d15eeafa9 in activemq's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f6d067a49 ] Merge pull request #1204 from mattrpav/AMQ-9430 [AMQ-9430] RuntimeConfigPlugin wire in classloader to JAXBContext > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > #
[jira] [Commented] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836231#comment-17836231
]
ASF subversion and git services commented on AMQ-9473:
--
Commit 9b81a7601014be8e90c889a3300fecf698d857fb in activemq's branch
refs/heads/activemq-5.18.x from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=9b81a7601 ]
AMQ-9473: Fix IntrospectionSupport to deal with SSLSocket properties
(cherry picked from commit 550cb9b2be32e5a6454e7bee5e31632498626a9c)
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
>
[jira] [Commented] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836229#comment-17836229
]
ASF subversion and git services commented on AMQ-9473:
--
Commit 550cb9b2be32e5a6454e7bee5e31632498626a9c in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=550cb9b2b ]
AMQ-9473: Fix IntrospectionSupport to deal with SSLSocket properties
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> test.ActiveMQClientSSLSocketParameter.main(ActiveMQClientSSLSocketParameter.java:25)
> [test/:?]
> {code}
> Here is example to reproduce issue:
>
[jira] [Commented] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836230#comment-17836230
]
ASF subversion and git services commented on AMQ-9473:
--
Commit 1c3c1289bbc4a4d4b6e7030210cf9dc6d2e2f038 in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=1c3c1289b ]
Merge pull request #1202 from jbonofre/AMQ-9473
AMQ-9473: Fix IntrospectionSupport to deal with SSLSocket properties
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> test.ActiveMQClientSSLSocketParameter.main(ActiveMQClientSSLSocketParameter.java:25)
> [test/:?]
> {code}
[jira] [Commented] (ARTEMIS-4722) Exclude netty-tcnative-boringssl-static artifacts
[ https://issues.apache.org/jira/browse/ARTEMIS-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836223#comment-17836223 ] ASF subversion and git services commented on ARTEMIS-4722: -- Commit 2db7940327548d96cda5e9b801e65004ac7c8371 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2db7940327 ] ARTEMIS-4722 Exclude netty-tcnative-boringssl-static artifacts The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned with the netty-tcnative-version in pom.xml. Those artifacts are included because of zookeeper-server. > Exclude netty-tcnative-boringssl-static artifacts > - > > Key: ARTEMIS-4722 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4722 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.33.0 >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned > with the netty-tcnative-version in pom.xml. Those artifacts are included > because of zookeeper-server. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836208#comment-17836208 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit 7702b39374d16816a096a0b282c29249ca2cee00 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7702b39374 ] ARTEMIS-4498 Adding internal column on address view > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836207#comment-17836207 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit 51f39fc34d1f7c5c5b8797ffca2640161950064c in activemq-artemis's branch refs/heads/main from a181321 [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=51f39fc34d ] ARTEMIS-4498 Expose internal queues for management and observability > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836210#comment-17836210 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit e1bf8222e7029fcd3fa8a51f5676e318a3d01740 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e1bf8222e7 ] ARTEMIS-4498 Adding release doc > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836209#comment-17836209 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit 162c4f6655dd4a513c1dfd491ebaa24ea817c414 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=162c4f6655 ] ARTEMIS-4498 Making queues always manageable > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4721) Possible documentation error in wildcard syntax recommendation
[
https://issues.apache.org/jira/browse/ARTEMIS-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836203#comment-17836203
]
ASF subversion and git services commented on ARTEMIS-4721:
--
Commit 6e3c7e055d80f82397dd427013fd234f1fdee029 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6e3c7e055d ]
ARTEMIS-4721 fix MQTT link in upgrade instructions
> Possible documentation error in wildcard syntax recommendation
> --
>
> Key: ARTEMIS-4721
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4721
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Priority: Minor
>
> The [user manual for version
> 2.33.0|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#wildcard-subscriptions]
> makes the recommendation to use the following configuration to match the
> MQTT specification for better performance:
> {code:java}
>
>/
>#
>*
> {code}
> Shouldn't it recommend "+" instead of "*" for single levels?
> Additionally, it would be good to clarify where this XML node is supposed to
> go. Top level? Inside {{{}{}}}? Inside {{{}{}}}?
> Somewhere else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4721) Possible documentation error in wildcard syntax recommendation
[
https://issues.apache.org/jira/browse/ARTEMIS-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836201#comment-17836201
]
ASF subversion and git services commented on ARTEMIS-4721:
--
Commit 221420b0b82ed912818b74c9d38f1982fc019153 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=221420b0b8 ]
ARTEMIS-4721 mqtt doc fixes
> Possible documentation error in wildcard syntax recommendation
> --
>
> Key: ARTEMIS-4721
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4721
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Priority: Minor
>
> The [user manual for version
> 2.33.0|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#wildcard-subscriptions]
> makes the recommendation to use the following configuration to match the
> MQTT specification for better performance:
> {code:java}
>
>/
>#
>*
> {code}
> Shouldn't it recommend "+" instead of "*" for single levels?
> Additionally, it would be good to clarify where this XML node is supposed to
> go. Top level? Inside {{{}{}}}? Inside {{{}{}}}?
> Somewhere else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836197#comment-17836197 ] ASF subversion and git services commented on AMQ-9330: -- Commit dc892d3dfc2f4b7d0402d947f40431ce4e50d92d in activemq's branch refs/heads/activemq-5.18.x from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=dc892d3df ] AMQ-9330 - Return 204 code when polling empty destinations (#1203) Previously a timeout was thrown and complete was not called so Jetty was returning a 500 error (cherry picked from commit 8b6072d03e273b02288e71cac6eef0539c48ea02) (cherry picked from commit 45a1bd54d3e1202d775388cf5b7d63e4c96183a5) > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836196#comment-17836196 ] ASF subversion and git services commented on AMQ-9330: -- Commit 8b6072d03e273b02288e71cac6eef0539c48ea02 in activemq's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=8b6072d03 ] AMQ-9330 - Return 204 code when polling empty destinations (#1203) Previously a timeout was thrown and complete was not called so Jetty was returning a 500 error > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9475) ConsumerControl commands for wildcard consumers should not auto-create destinations
[ https://issues.apache.org/jira/browse/AMQ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836119#comment-17836119 ] ASF subversion and git services commented on AMQ-9475: -- Commit a37c111a7522ab0307fc2bba877ce820538f5c3c in activemq's branch refs/heads/activemq-5.18.x from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a37c111a7 ] AMQ-9475 - ConsumerControl commands should not auto create wildcard dests This fixes an issue where wildcard destinations could be inadvertently created by ConsumerControl commands which could lead to problems. The processing logic for this command now will only look up existing destinations if they exist. > ConsumerControl commands for wildcard consumers should not auto-create > destinations > --- > > Key: AMQ-9475 > URL: https://issues.apache.org/jira/browse/AMQ-9475 > Project: ActiveMQ Classic > Issue Type: Bug >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 6.2.0, 5.18.5, 6.1.2 > > Time Spent: 50m > Remaining Estimate: 0h > > While investigating AMQ-9472, it was > [pointed|https://github.com/apache/activemq/pull/1198#issuecomment-2046523027] > out in some cases (like with Stomp) wildcard destinations that do not exist > could be auto created on subscribe which besides creating the extra > destination, can also lead to errors if proper ACLs are not set up. > As > [pointed|https://github.com/apache/activemq/pull/1198#issuecomment-2047625950] > out, the bug here is that wildcard destinations should not be auto-created > just by subscribing using a wildcard. There is a check for this in > [addConsumer()|https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L344-L346] > but > [processConsumerControl()|https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L694] > does not have the checks. So any time that command is sent (like prefetch > update) this could be an issue. > This can be fixed by only looking up destinations that are wildcards and not > auto creating them when processing consumer control objects just like > addConsumer() does. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9475) ConsumerControl commands for wildcard consumers should not auto-create destinations
[ https://issues.apache.org/jira/browse/AMQ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836114#comment-17836114 ] ASF subversion and git services commented on AMQ-9475: -- Commit c8f0419fff316ec7737b1707f5045d3166c0a61e in activemq's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=c8f0419ff ] AMQ-9475 - ConsumerControl commands should not auto create wildcard dests This fixes an issue where wildcard destinations could be inadvertently created by ConsumerControl commands which could lead to problems. The processing logic for this command now will only look up existing destinations if they exist. > ConsumerControl commands for wildcard consumers should not auto-create > destinations > --- > > Key: AMQ-9475 > URL: https://issues.apache.org/jira/browse/AMQ-9475 > Project: ActiveMQ Classic > Issue Type: Bug >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 6.2.0, 5.18.5, 6.1.2 > > Time Spent: 50m > Remaining Estimate: 0h > > While investigating AMQ-9472, it was > [pointed|https://github.com/apache/activemq/pull/1198#issuecomment-2046523027] > out in some cases (like with Stomp) wildcard destinations that do not exist > could be auto created on subscribe which besides creating the extra > destination, can also lead to errors if proper ACLs are not set up. > As > [pointed|https://github.com/apache/activemq/pull/1198#issuecomment-2047625950] > out, the bug here is that wildcard destinations should not be auto-created > just by subscribing using a wildcard. There is a check for this in > [addConsumer()|https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L344-L346] > but > [processConsumerControl()|https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L694] > does not have the checks. So any time that command is sent (like prefetch > update) this could be an issue. > This can be fixed by only looking up destinations that are wildcards and not > auto creating them when processing consumer control objects just like > addConsumer() does. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9475) ConsumerControl commands for wildcard consumers should not auto-create destinations
[ https://issues.apache.org/jira/browse/AMQ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836115#comment-17836115 ] ASF subversion and git services commented on AMQ-9475: -- Commit 78d95552338db1be2b95fc5c2fdd4eae8d045458 in activemq's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=78d955523 ] Merge pull request #1200 from cshannon/AMQ-9475 AMQ-9475 - ConsumerControl commands should not auto create wildcard dests > ConsumerControl commands for wildcard consumers should not auto-create > destinations > --- > > Key: AMQ-9475 > URL: https://issues.apache.org/jira/browse/AMQ-9475 > Project: ActiveMQ Classic > Issue Type: Bug >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 6.2.0, 5.18.5, 6.1.2 > > Time Spent: 50m > Remaining Estimate: 0h > > While investigating AMQ-9472, it was > [pointed|https://github.com/apache/activemq/pull/1198#issuecomment-2046523027] > out in some cases (like with Stomp) wildcard destinations that do not exist > could be auto created on subscribe which besides creating the extra > destination, can also lead to errors if proper ACLs are not set up. > As > [pointed|https://github.com/apache/activemq/pull/1198#issuecomment-2047625950] > out, the bug here is that wildcard destinations should not be auto-created > just by subscribing using a wildcard. There is a check for this in > [addConsumer()|https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L344-L346] > but > [processConsumerControl()|https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L694] > does not have the checks. So any time that command is sent (like prefetch > update) this could be an issue. > This can be fixed by only looking up destinations that are wildcards and not > auto creating them when processing consumer control objects just like > addConsumer() does. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9469) Removing JRMS dependency from assembly POM
[
https://issues.apache.org/jira/browse/AMQ-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836033#comment-17836033
]
ASF subversion and git services commented on AMQ-9469:
--
Commit f90c10df8e140ab97aaa42eb18107e8a18b80c8b in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f90c10df8 ]
Merge pull request #1191 from kartg/remove-assembly-jrms
[AMQ-9469] Removed JRMS-1.1 dependency from assembly pom.xml
> Removing JRMS dependency from assembly POM
> --
>
> Key: AMQ-9469
> URL: https://issues.apache.org/jira/browse/AMQ-9469
> Project: ActiveMQ Classic
> Issue Type: Improvement
> Environment: Tested using the libraries from the ActiveMQ 5.18.3
> tarball downloaded from
> https://activemq.apache.org/components/classic/download/
>Reporter: Kartik Ganesh
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 6.2.0, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Hello!
> I noticed that the ActiveMQ [assembly
> pom.xml|https://github.com/apache/activemq/blob/main/assembly/pom.xml#L484-L486]
> has a dependency on a very old library - "jrms-1.1" - and I'm wondering if
> this can be removed. This library has not seen any releases/updates since
> 2005 and [Maven|https://mvnrepository.com/artifact/jrms/jrms/usages] lists
> only ActiveMQ and Apache Camel as upstream usages.
> After digging through ActiveMQ's mailing lists and commit history, I found
> that it [used to be
> listed|https://github.com/apache/activemq-web/blob/7a7d976c/2004/06/23/jgroups-and-jrms-support.xml]
> on ActiveMQ's [URI
> Protocols|https://activemq.apache.org/components/classic/documentation/uri-protocols]
> page, but was removed at some point. JRMS seems to be listed as a
> peer-to-peer option on the
> [topologies|https://activemq.apache.org/components/classic/documentation/topologies]
> page but is not discussed in either the
> [peer|https://activemq.apache.org/components/classic/documentation/peer-transport-reference]
> or
> [multicast|https://activemq.apache.org/components/classic/documentation/multicast-transport-reference]
> transport reference pages.
> If I try to specify "jrms://" as a protocol for my ActiveMQConnectionFactory,
> I see the following stack-trace:
> {noformat}
> javax.jms.JMSException: Could not create Transport. Reason:
> java.io.IOException: Transport scheme NOT recognized: [jrms]
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:378)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:391)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> at App$HelloWorldProducer.run(App.java:66)
> at java.base/java.lang.Thread.run(Thread.java:840)
> Caused by: java.io.IOException: Transport scheme NOT recognized: [jrms]
> at
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:30)
> at
> org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:185)
> at
> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:376)
> ... 5 more
> Caused by: java.io.IOException: Could not find factory class for resource:
> META-INF/services/org/apache/activemq/transport/jrms
> at
> org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:104)
> at
> org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:61)
> at
> org.apache.activemq.util.FactoryFinder.newInstance(FactoryFinder.java:154)
> at
> org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:182)
> ... 7 more{noformat}
> An [email from 2011 on the users
> mailing-list|https://lists.apache.org/thread/wbwdj8011tmcqtdlbbfmzsthjdrh0gn0]
> came to the same conclusion, but I don't see any further discussion on it.
> I've confirmed that the
> [META-INF/services/org/apache/activemq/transport|https://github.com/apache/activemq/tree/main/activemq-client/src/main/resources/META-INF/services/org/apache/activemq/transport]
> folder under activemq-client does not have a "jrms" file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1634) Coverity: Unintentional integer overflow (OVERFLOW_BEFORE_WIDEN) in QueueControlImpl.java
[
https://issues.apache.org/jira/browse/ARTEMIS-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835977#comment-17835977
]
ASF subversion and git services commented on ARTEMIS-1634:
--
Commit b2ffe9ff5743cf65bfd5b60a5e25951cd36fa547 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=b2ffe9ff57 ]
ARTEMIS-1634 unintentional integer overflow
> Coverity: Unintentional integer overflow (OVERFLOW_BEFORE_WIDEN) in
> QueueControlImpl.java
> -
>
> Key: ARTEMIS-1634
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1634
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.5.0
>Reporter: Jiri Daněk
>Priority: Major
>
> {noformat}
>@Override
>public CompositeData[] browse(int page, int pageSize) throws Exception {
> String filter = null;
> checkStarted();
> clearIO();
> try {
> long index = 0;
> CID 1464349 (#1 of 2): Unintentional integer overflow (OVERFLOW_BEFORE_WIDEN)
> [select issue]
> long start = (page - 1) * pageSize;
> CID 1464349 (#2 of 2): Unintentional integer overflow
> (OVERFLOW_BEFORE_WIDEN)overflow_before_widen: Potentially
> overflowing expression page * pageSize with type int (32 bits, signed) is
> evaluated using 32-bit arithmetic, and then used
> in a context that expects an expression of type long (64 bits, signed). To
> avoid overflow, cast either page or pageSize to
> type long rather than casting the result of the potential overflow.
> long end = Math.min((long)(page * pageSize),
> queue.getMessageCount());
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4675) Add replication status metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835902#comment-17835902 ] ASF subversion and git services commented on ARTEMIS-4675: -- Commit 33599f772749bc76d1a7f7deb9a529faf8fa252e in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=33599f7727 ] ARTEMIS-4675 fix and improving test > Add replication status metrics > -- > > Key: ARTEMIS-4675 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4675 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Clustering >Affects Versions: 2.32.0 >Reporter: Alvin Kwekel >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > Add metrics to be able to monitor the cluster replication status. > Somewhat related to feature request ARTEMIS-4479. > I've created a PR for this: > https://github.com/apache/activemq-artemis/pull/4844 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9470) ActiveMQ JMX / Jolokia - Log4j reloadLog4jProperties yields NoSuchMethodExpection
[ https://issues.apache.org/jira/browse/AMQ-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835877#comment-17835877 ] ASF subversion and git services commented on AMQ-9470: -- Commit 04e84afa891123ead07dbccb0b21f0ca80666e65 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=04e84afa8 ] Merge pull request #1197 from AM-19/branch2 [AMQ-9470] Updated Methods to be called, to properly reload Log4j Properties > ActiveMQ JMX / Jolokia - Log4j reloadLog4jProperties yields > NoSuchMethodExpection > - > > Key: AMQ-9470 > URL: https://issues.apache.org/jira/browse/AMQ-9470 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.3, 6.1.0 >Reporter: Anubhav Mishra >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > The Log4jConfiguration's JMX method to reload the log4j properties yield > NoSuchMethodException. > As the method resetConfiguration no longer exists, in LogManager. > > Steps to reproduce: > > # Start ActiveMQ > # Trigger JMX Method: reloadLog4jProperties > or Execute: > [host:8161/api/jolokia/exec/org.apache.activemq:type=Broker,brokerName=localhost,service=Log4JConfiguration/reloadLog4jProperties()|http://localhost:8161/api/jolokia/exec/org.apache.activemq:type=Broker,brokerName=localhost,service=Log4JConfiguration/reloadLog4jProperties()] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9470) ActiveMQ JMX / Jolokia - Log4j reloadLog4jProperties yields NoSuchMethodExpection
[ https://issues.apache.org/jira/browse/AMQ-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835876#comment-17835876 ] ASF subversion and git services commented on AMQ-9470: -- Commit d15dedf4e3437dd0943eb7590684528a7f57d6e3 in activemq's branch refs/heads/main from AM-19 [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=d15dedf4e ] [AMQ-9470] Updated Methods to be called, to properly reload Log4j Properties > ActiveMQ JMX / Jolokia - Log4j reloadLog4jProperties yields > NoSuchMethodExpection > - > > Key: AMQ-9470 > URL: https://issues.apache.org/jira/browse/AMQ-9470 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.3, 6.1.0 >Reporter: Anubhav Mishra >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > The Log4jConfiguration's JMX method to reload the log4j properties yield > NoSuchMethodException. > As the method resetConfiguration no longer exists, in LogManager. > > Steps to reproduce: > > # Start ActiveMQ > # Trigger JMX Method: reloadLog4jProperties > or Execute: > [host:8161/api/jolokia/exec/org.apache.activemq:type=Broker,brokerName=localhost,service=Log4JConfiguration/reloadLog4jProperties()|http://localhost:8161/api/jolokia/exec/org.apache.activemq:type=Broker,brokerName=localhost,service=Log4JConfiguration/reloadLog4jProperties()] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9474) Update activemq-osgi import for Spring 6
[ https://issues.apache.org/jira/browse/AMQ-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835874#comment-17835874 ] ASF subversion and git services commented on AMQ-9474: -- Commit 34432e2b7ac13f45540cf709bf02058498b5de51 in activemq's branch refs/heads/main from Matt Pavlovich [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=34432e2b7 ] [AMQ-9474] Update activemq-osgi import for Spring 6 > Update activemq-osgi import for Spring 6 > > > Key: AMQ-9474 > URL: https://issues.apache.org/jira/browse/AMQ-9474 > Project: ActiveMQ Classic > Issue Type: Task > Components: OSGi/Karaf >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.2.0, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Support wiring ActiveMQ to Spring 6 in Apache Karaf 4.4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9474) Update activemq-osgi import for Spring 6
[ https://issues.apache.org/jira/browse/AMQ-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835875#comment-17835875 ] ASF subversion and git services commented on AMQ-9474: -- Commit d0dac1792692df34a94cdd89edfba64df2c1aa2b in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=d0dac1792 ] Merge pull request #1199 from mattrpav/AMQ-9474 [AMQ-9474] Update activemq-osgi import for Spring 6 > Update activemq-osgi import for Spring 6 > > > Key: AMQ-9474 > URL: https://issues.apache.org/jira/browse/AMQ-9474 > Project: ActiveMQ Classic > Issue Type: Task > Components: OSGi/Karaf >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.2.0, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Support wiring ActiveMQ to Spring 6 in Apache Karaf 4.4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9476) Jetty config has invalid constraint mapping
[ https://issues.apache.org/jira/browse/AMQ-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835869#comment-17835869 ] ASF subversion and git services commented on AMQ-9476: -- Commit 43cc596219b6a8c8b5a54fbda3fb68cb4424f2d0 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=43cc59621 ] Merge pull request #1201 from cshannon/AMQ-9476 AMF-9476 - Fix Jetty constraint mapping > Jetty config has invalid constraint mapping > --- > > Key: AMQ-9476 > URL: https://issues.apache.org/jira/browse/AMQ-9476 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 6.1.1 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > > Fix constraint mapping that is incorrect -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4675) Add replication status metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835845#comment-17835845 ] ASF subversion and git services commented on ARTEMIS-4675: -- Commit 6976c075bebc4f8cfaa2b060157ad907f8ddca87 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6976c075be ] ARTEMIS-4675 fix test > Add replication status metrics > -- > > Key: ARTEMIS-4675 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4675 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Clustering >Affects Versions: 2.32.0 >Reporter: Alvin Kwekel >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > Add metrics to be able to monitor the cluster replication status. > Somewhat related to feature request ARTEMIS-4479. > I've created a PR for this: > https://github.com/apache/activemq-artemis/pull/4844 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4718) Diverted messages are not properly routed on cluster remote bindings
[ https://issues.apache.org/jira/browse/ARTEMIS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835813#comment-17835813 ] ASF subversion and git services commented on ARTEMIS-4718: -- Commit 48f17e998649b95cb5beee34f520aaec544b447b in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=48f17e9986 ] ARTEMIS-4718 Diverted messages are not propertly routed on cluster remote bindings I commented the fix to validate the test and I accidently committed the commented out version > Diverted messages are not properly routed on cluster remote bindings > > > Key: ARTEMIS-4718 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4718 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4675) Add replication status metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835539#comment-17835539 ] ASF subversion and git services commented on ARTEMIS-4675: -- Commit b9c919821beea8ca501b7cc30d61866332590629 in activemq-artemis's branch refs/heads/main from Alvin Kwekel [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=b9c919821b ] ARTEMIS-4675 Add replication status metrics > Add replication status metrics > -- > > Key: ARTEMIS-4675 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4675 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Clustering >Affects Versions: 2.32.0 >Reporter: Alvin Kwekel >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Add metrics to be able to monitor the cluster replication status. > Somewhat related to feature request ARTEMIS-4479. > I've created a PR for this: > https://github.com/apache/activemq-artemis/pull/4844 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4715) Using # wildcard from OpenWire JMS consumer stopped working with 2.33.0
[ https://issues.apache.org/jira/browse/ARTEMIS-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835527#comment-17835527 ] ASF subversion and git services commented on ARTEMIS-4715: -- Commit d3e5b70d90f8d21e5e7630c22ae4e14d66fcbea4 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=d3e5b70d90 ] ARTEMIS-4715 using # wildcard from OpenWire JMS consumer stopped working > Using # wildcard from OpenWire JMS consumer stopped working with 2.33.0 > --- > > Key: ARTEMIS-4715 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4715 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.33.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Attachments: camel-activemq-test-artemis-2.32.log, > camel-activemq-test-artemis-2.33.log > > Time Spent: 20m > Remaining Estimate: 0h > > One of our > [tests|https://github.com/apache/camel/blob/main/components/camel-activemq/src/test/java/org/apache/camel/component/activemq/ActiveMQRouteIT.java#L66-L71] > that [consumes data from a wildcard > queue|https://github.com/apache/camel/blob/main/components/camel-activemq/src/test/java/org/apache/camel/component/activemq/ActiveMQRouteIT.java#L111-L113] > has stopped working after migrating to Artemis 2.33.0. > > This test works without problems when using Artemis 2.32.0. I attached the > logs from executing the test with 2.32 and 2.33. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4717) Upgrade commons-configuration2 to 2.10.1
[ https://issues.apache.org/jira/browse/ARTEMIS-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835018#comment-17835018 ] ASF subversion and git services commented on ARTEMIS-4717: -- Commit 9583f844c17ff3463327f5e0ae209ef10cfa4c0f in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9583f844c1 ] ARTEMIS-4717 Upgrade commons-configuration2 to 2.10.1 > Upgrade commons-configuration2 to 2.10.1 > > > Key: ARTEMIS-4717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4717 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4718) Diverted messages are not properly routed on cluster remote bindings
[ https://issues.apache.org/jira/browse/ARTEMIS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835016#comment-17835016 ] ASF subversion and git services commented on ARTEMIS-4718: -- Commit a723f634a28938b85326079efb4cdc02550be428 in activemq-artemis's branch refs/heads/main from AntonRoskvist [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=a723f634a2 ] ARTEMIS-4718 Diverted messages are not propertly routed on cluster remote bindings > Diverted messages are not properly routed on cluster remote bindings > > > Key: ARTEMIS-4718 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4718 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4510) Add auto-create-destination logic to diverts
[ https://issues.apache.org/jira/browse/ARTEMIS-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834955#comment-17834955 ] ASF subversion and git services commented on ARTEMIS-4510: -- Commit 6c02950db386b0dcb7b9539a0f63f20fa5be00cd in activemq-artemis's branch refs/heads/main from AntonRoskvist [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6c02950db3 ] ARTEMIS-4510 Add auto-create-destination logic to diverts > Add auto-create-destination logic to diverts > > > Key: ARTEMIS-4510 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4510 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 4h 40m > Remaining Estimate: 0h > > This enables the use of dynamic routing decisions within the transformer by > setting the message address. It also covers for a rare problem where if any > of the forwarding addresses are removed during runtime, such as from > auto-delete, the message would get silently dropped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4582) add view and edit permissions to extend security-settings rbac for management operations
[ https://issues.apache.org/jira/browse/ARTEMIS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834884#comment-17834884 ] ASF subversion and git services commented on ARTEMIS-4582: -- Commit 4d6fc39560d0d26fdbecea14de74eee35f2941f9 in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=4d6fc39560 ] ARTEMIS-4582 doc update to make need to remove auth section of management.xml more clear > add view and edit permissions to extend security-settings rbac for management > operations > > > Key: ARTEMIS-4582 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4582 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker, Configuration, JMX, Web Console >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.33.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > we have the manage permission that allows sending to the management address, > to access any control resource. We don't however distinguish what a user can > do. > We should segment control operations into categories: CRUD provides a basis > view for get/is (Read) > edit for set or operations that mutate or modify. > We allow this sort of configuration via management.xml for jmx mbean access > but using a different model based on object name. > All of the mbeans delegate to the control resources. > If we add these two additional permissions then we can have a single rbac > model (that supports config reload) and more granularity on control resource > access from the management address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4666) Federated queue consumers do not receive messages on classic clients
[ https://issues.apache.org/jira/browse/ARTEMIS-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834383#comment-17834383 ] ASF subversion and git services commented on ARTEMIS-4666: -- Commit 2c3f77264594f11f2bf0047bc16f2b1cb26d577e in activemq-artemis's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2c3f772645 ] ARTEMIS-4666 Correctly set queue match when parsing XML confing Correct the XML parser for core federation queue match policy loading to call the setQueueMatch instead of setAddressMatch when reading the queue match element. > Federated queue consumers do not receive messages on classic clients > > > Key: ARTEMIS-4666 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4666 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Federation >Affects Versions: 2.32.0 >Reporter: Josh Byster >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.34.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Federated queues with A upstream and downstream to B do not seem to work as > expected when the client JMS implementation is ActiveMQ Classic v5.16.2 (used > in my example, but also verified the issue is present with v5.18.3 and > v6.0.1). With Artemis JMS as the client, it seems to work as expected. > When running a producer on A and a consumer on B with the classic > org.apache.activemq.ActiveMQConnectionFactory, the consumer on B does not > consume any messages that the producer sends. When B is restarted, it then > consumes the messages. > This works properly with ActiveMQ Artemis > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory. I've > created a minimal reproducible example > [here|https://github.com/josh-byster/artemis-classic-consumer-bug/tree/master]. > Running server1 and server2 and then first starting up the Consumer then > running the Producer class, we can see that no messages are logged in console > by the consumer. When you restart the consumer, the messages are consumed. > This is an issue whether you attach a MessageListener or you call receive() > directly. If you switch the ActiveMQConnectionFactory implementation to > Artemis, it works as expected. > I don't think this necessarily warrants a fix if it's an issue specifically > with the classic client, since the solution is just to upgrade clients to > Artemis. However, if it is something that can be patched on the server, that > would be great. I do, however, think it would be good to note this down in > the docs that it's not supported with classic clients, since I spent a while > debugging it. However, most other features do work as expected with the > clients running the classic version, which is much appreciated as it makes > migration significantly easier. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4652) Rollback of XAResource implementation should never return XA_RETRY
[
https://issues.apache.org/jira/browse/ARTEMIS-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834377#comment-17834377
]
ASF subversion and git services commented on ARTEMIS-4652:
--
Commit a128e46337f65d82b38898df0042d65b22ae3ff2 in activemq-artemis's branch
refs/heads/main from Emmanuel Hugonnet
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=a128e46337 ]
ARTEMIS-4652 When the error is of type XAER_NOTA we shouldn't close the
connection in case some recovery is happening.
Signed-off-by: Emmanuel Hugonnet
> Rollback of XAResource implementation should never return XA_RETRY
> --
>
> Key: ARTEMIS-4652
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4652
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> According to [the XA
> spec|https://pubs.opengroup.org/onlinepubs/009680699/toc.pdf] {{XA_RETRY}} is
> not a valid response from {{xa_rollback}}. We should return {{XAER_RMFAIL}}
> instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4712) Remove LDAP connection pooling
[
https://issues.apache.org/jira/browse/ARTEMIS-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834312#comment-17834312
]
ASF subversion and git services commented on ARTEMIS-4712:
--
Commit baa8710fa2180b62bd31e51bcc57e160006b1ff4 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=baa8710fa2 ]
ARTEMIS-4712 remove LDAP connection pooling
> Remove LDAP connection pooling
> --
>
> Key: ARTEMIS-4712
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4712
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{LDAPLoginModule}} supports connection pooling, but there have been
> reports of weird behavior with pooling vs. without. For example, with pooling
> once a login failure occurs subsequent login attempts also fail - even if
> credentials are valid. However, without pooling this behavior is never seen.
> Upon further investigation the [Oracle
> documentation|https://docs.oracle.com/javase/jndi/tutorial/ldap/connect/pool.html]
> says this:
> bq. Pooled connections are intended to be reused. Therefore, if you plan to
> perform operations on a Context instance that might alter the underlying
> connection's state, then you should not use connection pooling for that
> Context instance. For example, if you plan to invoke the Start TLS extended
> operation on a Context instance, or plan to change security-related
> properties (such as "java.naming.security.principal" or
> "java.naming.security.protocol") after the initial context has been created,
> you should not use connection pooling for that Context instance because the
> LDAP provider does not track any such state changes. If you use connection
> pooling in such situations, you might be compromising the security of your
> application.
> The {{LDAPLoginModule}} does, in fact, modify the
> {{java.naming.security.principal}} of the {{Context}} (i.e. in the
> {{bindUser}} method). Although the {{Context}} is immediately reset to the
> original values (ostensibly restoring normal pool behavior) the pooling
> functionality should be removed in an abundance of caution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4714) Mitigate NPE in FederatedQueueConsumerImpl MessageListener
[ https://issues.apache.org/jira/browse/ARTEMIS-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834311#comment-17834311 ] ASF subversion and git services commented on ARTEMIS-4714: -- Commit 0fad7ece876a8afbf419b8fb4a7c6de8878d1141 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0fad7ece87 ] ARTEMIS-4714 mitigate NPE in FederatedQueueConsumerImpl MessageListener > Mitigate NPE in FederatedQueueConsumerImpl MessageListener > -- > > Key: ARTEMIS-4714 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4714 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4704) Eliminate unnecessary variable in ReplicationManager
[ https://issues.apache.org/jira/browse/ARTEMIS-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834086#comment-17834086 ] ASF subversion and git services commented on ARTEMIS-4704: -- Commit da9695a5f6c3bbeb6fead7658e516895eca15e04 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=da9695a5f6 ] ARTEMIS-4704 eliminate unnecessary variable in ReplicationManager > Eliminate unnecessary variable in ReplicationManager > > > Key: ARTEMIS-4704 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4704 > Project: ActiveMQ Artemis > Issue Type: Improvement >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-4713) Mitigate NPE in LargeMessageControllerImpl
[
https://issues.apache.org/jira/browse/ARTEMIS-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834085#comment-17834085
]
ASF subversion and git services commented on ARTEMIS-4713:
--
Commit 9f50aff46ddde8cec612528181e91bb4205b133d in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9f50aff46d ]
ARTEMIS-4713 mitigate NPE in LargeMessageControllerImpl
> Mitigate NPE in LargeMessageControllerImpl
> --
>
> Key: ARTEMIS-4713
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4713
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The semantics of the {{take}} method changed in ARTEMIS-4588 making a
> {{NullPointerException}} possible. The original semantics should be restored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4711) XmlDataImporter now requires JMS code
[ https://issues.apache.org/jira/browse/ARTEMIS-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834073#comment-17834073 ] ASF subversion and git services commented on ARTEMIS-4711: -- Commit 604c6d3d90be437282ce58b33111b48ae193a4cf in activemq-artemis's branch refs/heads/main from Emmanuel Hugonnet [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=604c6d3d90 ] ARTEMIS-4711 removing the dependency on JMS code by XmlDataImporter Introducing ConnectionConfigurationAbtract to expose the configuration to connect to a broker without requiring the JMS code. Signed-off-by: Emmanuel Hugonnet > XmlDataImporter now requires JMS code > - > > Key: ARTEMIS-4711 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4711 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.33.0 >Reporter: Emmanuel Hugonnet >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The fix to ARTEMIS-4689 makes the XmlDataImporter code dependant over JMS > code thus making it unusable in a JakartaEE environment while the effective > usage of that JMS code is none. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4710) Keep pem-keystore dependencies as is; make it really optional
[ https://issues.apache.org/jira/browse/ARTEMIS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833260#comment-17833260 ] ASF subversion and git services commented on ARTEMIS-4710: -- Commit bf1ea4128775c97e6c6fc6a0ab6921feaf8197d5 in activemq-artemis's branch refs/heads/main from Alexey Markevich [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=bf1ea41287 ] ARTEMIS-4710 Keep pem-keystore dependencies as is; make it really optional The latest version already uses bcprov-jdk18on. Avoid global imports to be able to exclude dependency when not used. > Keep pem-keystore dependencies as is; make it really optional > - > > Key: ARTEMIS-4710 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4710 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.33.0 >Reporter: Alexey Markevich >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Previously we excluded bcprov-jdk15on and bcpkix-jdk15on dependencies > normally used by pem-keystore, and replaced them with bcprov-jdk18on and > bcpkix-jdk18on as already managed and used elsewhere in the build, thus > keeping things consistent on a single gav for the bc modules. > The latest 2.3.0 version of pem-keystore (used since ARTEMIS-4599) was > actually changed to use bcprov-jdk18on and bcpkix-jdk18on in > https://github.com/ctron/pem-keystore/commit/1263b207da0adf4a7d2dc61d6a9a19e7bba97731. > As such we can now simplify the dependency handling by removing the prior > exclusion+replacement handling for those deps. > Additionally, by avoiding a global import on PemKeyStoreProvider, and only > referencing it upon use, those who wish would be able to exclude the > dependency when the functionality is not used. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4698) MetricsManagers' remove method may cause a NullPointerException
[
https://issues.apache.org/jira/browse/ARTEMIS-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832952#comment-17832952
]
ASF subversion and git services commented on ARTEMIS-4698:
--
Commit f36e944641b8642c5acab55c2076871e86f59c70 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=f36e944641 ]
ARTEMIS-4698 mitigate NPE when removing metrics
> MetricsManagers' remove method may cause a NullPointerException
>
>
> Key: ARTEMIS-4698
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4698
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.27.0, 2.27.1, 2.28.0, 2.29.0, 2.30.0, 2.31.0, 2.31.1,
> 2.31.2, 2.32.0, 2.33.0
>Reporter: Jelle Smits
>Assignee: Justin Bertram
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I recently switched from Artemis-server 2.19.1 to 2.31.1. From this point, I
> have been experiencing a lot the following errors:
> {noformat}
> AMQ224065: Failed to remove auto-created queue xyz{noformat}
> The stack trace shows that this consistenly happens in the {{remove}} call of
> the {{MetricsManager}}. More specifically, the {{logger.debug}} statement
> which uses the {{removed}} variable:
> {noformat}
> java.lang.NullPointerException: Cannot invoke
> "io.micrometer.core.instrument.Meter.getId()" because "removed" is null
> at
> org.apache.activemq.artemis.core.server.metrics.MetricsManager.remove(MetricsManager.java:167){noformat}
> This did not happen in the previous version, as prior to ARTEMIS-4020 the log
> statement was conditional based on whether debug logging was enabled.
> While the issue at hand may be caused by my application (un)registering
> additional metrics on some queues, I feel the {{MeterRegistry}} should
> include a null-check for the value of removed, as by the JavaDoc of
> Micrometers' MeterRegistry, the meterRegistry.remove will return:
> bq. The removed meter, or null if the provided meter is not currently
> registered.
> Also, as a {{null}} from the {{MeterRegistry}} means that the metric no
> longer exists, as this is a remove call that should not be a blocking issue.
> I currently work around the issue using a class overload with an inline null
> check:
> {code:java}
> logger.debug("Unregistered meter: {}", removed != null ? removed.getId() :
> "null");{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4694) Servers should be resilient to large headers
[ https://issues.apache.org/jira/browse/ARTEMIS-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832939#comment-17832939 ] ASF subversion and git services commented on ARTEMIS-4694: -- Commit 04f6424928a3d9cbc26f6b26f7c2e9b7f7bf7869 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=04f6424928 ] ARTEMIS-4694 Redistribution issues with Almost Large Header Redistribution would add data to the record which would then in turn make the record too large to redistribute. The Redistributor and Bridges should not be removed. Also a warning should be added to warn users about the situation. > Servers should be resilient to large headers > > > Key: ARTEMIS-4694 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4694 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.32.0 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Users should not use large headers, but in case they did the server should > not be stopped or become unstable. Producers may get exceptions but the > server should still behave fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832858#comment-17832858
]
ASF subversion and git services commented on AMQ-9460:
--
Commit 661fce3f16df34879784556dbea5a1d9989ffed6 in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=661fce3f1 ]
AMQ-9460: Fix authentication on Docker images
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.1
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832859#comment-17832859
]
ASF subversion and git services commented on AMQ-9460:
--
Commit 2bdf0466d07e71964cf4de6ab0de8bb7e2b4f06a in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=2bdf0466d ]
Merge pull request #1196 from jbonofre/AMQ-9460
AMQ-9460: Fix authentication on Docker images
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.1
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832793#comment-17832793
]
ASF subversion and git services commented on AMQ-9460:
--
Commit 3636a497ede5b95cf8257c2f359a3bc8a02fb325 in activemq's branch
refs/heads/activemq-6.0.x from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=3636a497e ]
Revert "AMQ-9460: Don't override ACTIVEMQ_OPTS when provided by user"
This reverts commit f761b6598ef91458e56a6b873ea9f753e1333e07.
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832791#comment-17832791
]
ASF subversion and git services commented on AMQ-9460:
--
Commit f47ae99fb98148737ec3a9c3712ec6a66b8c2426 in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f47ae99fb ]
Merge pull request #1195 from apache/revert-1193-AMQ-9460
Revert "AMQ-9460: Don't override ACTIVEMQ_OPTS when provided by user"
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832790#comment-17832790
]
ASF subversion and git services commented on AMQ-9460:
--
Commit 7cbe23974c729a538fd3971ee0de344f526bfee3 in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=7cbe23974 ]
Revert "AMQ-9460: Don't override ACTIVEMQ_OPTS when provided by user"
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832789#comment-17832789
]
ASF subversion and git services commented on AMQ-9460:
--
Commit 7cbe23974c729a538fd3971ee0de344f526bfee3 in activemq's branch
refs/heads/revert-1193-AMQ-9460 from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=7cbe23974 ]
Revert "AMQ-9460: Don't override ACTIVEMQ_OPTS when provided by user"
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.1
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832735#comment-17832735
]
ASF subversion and git services commented on AMQ-9460:
--
Commit f761b6598ef91458e56a6b873ea9f753e1333e07 in activemq's branch
refs/heads/activemq-6.0.x from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f761b6598 ]
AMQ-9460: Don't override ACTIVEMQ_OPTS when provided by user
(cherry picked from commit 34e228f14c01ba9c029369d4360ca02b3896dd98)
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.0, 6.1.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832734#comment-17832734
]
ASF subversion and git services commented on AMQ-9460:
--
Commit 24c00d1a806e3e263322db875f49b541c6df0c97 in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=24c00d1a8 ]
Merge pull request #1193 from jbonofre/AMQ-9460
AMQ-9460: Don't override ACTIVEMQ_OPTS when provided by user
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.0, 6.1.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9460) Running activemq-classic via docker does not allow access to web console
[
https://issues.apache.org/jira/browse/AMQ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832733#comment-17832733
]
ASF subversion and git services commented on AMQ-9460:
--
Commit 34e228f14c01ba9c029369d4360ca02b3896dd98 in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=34e228f14 ]
AMQ-9460: Don't override ACTIVEMQ_OPTS when provided by user
> Running activemq-classic via docker does not allow access to web console
>
>
> Key: AMQ-9460
> URL: https://issues.apache.org/jira/browse/AMQ-9460
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Docker
>Affects Versions: 6.0.1
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.0, 6.1.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I cannot use the web console when running via docker
> docker run -d -p 61616:61616 -p 8161:8161 apache/activemq-classic
> When you open localhost:8161 the web console comes up, but when you start
> browsing queues then the login page is shown. But admin/admin does not work.
> It works fine in the standalone .tar you can download and run locally.
> It seems the conf/credentials.properties is corrupted in the docker image vs
> standalone.
> Standalone
> {code}
> ~/Downloads/apache-activemq-6.1.0/conf ❯ cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=admin%
> {code}
> And on docker:
> {code}
> /opt/apache-activemq/conf
> root@8483a39f7510:/opt/apache-activemq/conf# cat users.properties
> ## ---
> ## Licensed to the Apache Software Foundation (ASF) under one or more
> ## contributor license agreements. See the NOTICE file distributed with
> ## this work for additional information regarding copyright ownership.
> ## The ASF licenses this file to You under the Apache License, Version 2.0
> ## (the "License"); you may not use this file except in compliance with
> ## the License. You may obtain a copy of the License at
> ##
> ## http://www.apache.org/licenses/LICENSE-2.0
> ##
> ## Unless required by applicable law or agreed to in writing, software
> ## distributed under the License is distributed on an "AS IS" BASIS,
> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ## See the License for the specific language governing permissions and
> ## limitations under the License.
> ## ---
> admin=adminroot@8483a39f7510:/opt/apache-activemq/conf#
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9458) Upgrade to Jetty 9.4.54.v20240208
[ https://issues.apache.org/jira/browse/AMQ-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832551#comment-17832551 ] ASF subversion and git services commented on AMQ-9458: -- Commit 91e2fad3653eaa94f0ace4663bd6c990753a2745 in activemq's branch refs/heads/activemq-5.17.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=91e2fad36 ] AMQ-9458: Upgrade to Jetty 9.4.54.v20240208 (cherry picked from commit ec4bde01fb683a205b0d3d71bc5bea256dc1eb16) > Upgrade to Jetty 9.4.54.v20240208 > - > > Key: AMQ-9458 > URL: https://issues.apache.org/jira/browse/AMQ-9458 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Transport, Web Console >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9458) Upgrade to Jetty 9.4.54.v20240208
[ https://issues.apache.org/jira/browse/AMQ-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832550#comment-17832550 ] ASF subversion and git services commented on AMQ-9458: -- Commit f358bb72131488583dacd8906101b20060828ad1 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f358bb721 ] Merge pull request #1180 from jbonofre/AMQ-9458 AMQ-9458: Upgrade to Jetty 9.4.54.v20240208 > Upgrade to Jetty 9.4.54.v20240208 > - > > Key: AMQ-9458 > URL: https://issues.apache.org/jira/browse/AMQ-9458 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Transport, Web Console >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9458) Upgrade to Jetty 9.4.54.v20240208
[ https://issues.apache.org/jira/browse/AMQ-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832549#comment-17832549 ] ASF subversion and git services commented on AMQ-9458: -- Commit ec4bde01fb683a205b0d3d71bc5bea256dc1eb16 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=ec4bde01f ] AMQ-9458: Upgrade to Jetty 9.4.54.v20240208 > Upgrade to Jetty 9.4.54.v20240208 > - > > Key: AMQ-9458 > URL: https://issues.apache.org/jira/browse/AMQ-9458 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Transport, Web Console >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9453) Upgrade to Spring 5.3.33
[ https://issues.apache.org/jira/browse/AMQ-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832548#comment-17832548 ] ASF subversion and git services commented on AMQ-9453: -- Commit 27e1efc51a184b7c5e5f113070ad60feff43ecd4 in activemq's branch refs/heads/activemq-5.17.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=27e1efc51 ] AMQ-9453: Upgrade to Spring 5.3.33 (cherry picked from commit eb71c70e57b218c98ae95129d2f75aaf9275cafb) > Upgrade to Spring 5.3.33 > > > Key: AMQ-9453 > URL: https://issues.apache.org/jira/browse/AMQ-9453 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9453) Upgrade to Spring 5.3.33
[ https://issues.apache.org/jira/browse/AMQ-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832546#comment-17832546 ] ASF subversion and git services commented on AMQ-9453: -- Commit eb71c70e57b218c98ae95129d2f75aaf9275cafb in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=eb71c70e5 ] AMQ-9453: Upgrade to Spring 5.3.33 > Upgrade to Spring 5.3.33 > > > Key: AMQ-9453 > URL: https://issues.apache.org/jira/browse/AMQ-9453 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9453) Upgrade to Spring 5.3.33
[ https://issues.apache.org/jira/browse/AMQ-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832547#comment-17832547 ] ASF subversion and git services commented on AMQ-9453: -- Commit 0b04b310532111d59e742b07680231686fb896e6 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=0b04b3105 ] Merge pull request #1179 from jbonofre/AMQ-9453 AMQ-9453: Upgrade to Spring 5.3.33 > Upgrade to Spring 5.3.33 > > > Key: AMQ-9453 > URL: https://issues.apache.org/jira/browse/AMQ-9453 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4696) Deprecate queue prefetch address setting
[ https://issues.apache.org/jira/browse/ARTEMIS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831450#comment-17831450 ] ASF subversion and git services commented on ARTEMIS-4696: -- Commit 774d321012c55fb2696257a7560228d995593fa0 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=774d321012 ] ARTEMIS-4696 Deprecate queue prefetch address setting > Deprecate queue prefetch address setting > > > Key: ARTEMIS-4696 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4696 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > The queue prefetch address setting was added by the commit [ARTEMIS-463 > Refactoring on > Openwire|https://github.com/apache/activemq-artemis/commit/6ddf486f8f17776e14cef0c37ca2c9a6a891be7a] > and it is only used for ActiveMQ 5 test purposes to check consumers with no > prefetch. It can be deprecated and replaced by the the default consumer > window size address setting. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4699) properties config - implied factoryClassName on TransportConfiguration can be wrong, it needs to be provided via a property value
[ https://issues.apache.org/jira/browse/ARTEMIS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831241#comment-17831241 ] ASF subversion and git services commented on ARTEMIS-4699: -- Commit 625bdfce6e80f802fa7aef4344b94fcf34055f3d in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=625bdfce6e ] ARTEMIS-4699 properties config don't try and imply the factoryClassName of a transport config object, fix up fluent builder and improve mirror usability > properties config - implied factoryClassName on TransportConfiguration can be > wrong, it needs to be provided via a property value > - > > Key: ARTEMIS-4699 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4699 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Configuration >Affects Versions: 2.33.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > > There is an incorrect setting of the factoryClassName for a transport > configuration. When initialised from a uri this is broken as the value is > already set and when used for acceptors it is plain wrong. > this default or implicit setting does not know the correct context, it should > be removed in favour of having it provided via the factoryClassName property > value -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4701) Update to Netty 4.1.108
[ https://issues.apache.org/jira/browse/ARTEMIS-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831018#comment-17831018 ] ASF subversion and git services commented on ARTEMIS-4701: -- Commit 19d77011de953ead80f17a6628280054d08f3363 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=19d77011de ] ARTEMIS-4701: update to Netty 4.1.108 (and netty-tcnative test dep to 2.0.65) > Update to Netty 4.1.108 > --- > > Key: ARTEMIS-4701 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4701 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Priority: Major > Fix For: 2.34.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9466) Upgrade to log4j 2.23.1
[ https://issues.apache.org/jira/browse/AMQ-9466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830788#comment-17830788 ] ASF subversion and git services commented on AMQ-9466: -- Commit 7962ccb6f092b7f64608c2e795d69cde1645ef94 in activemq's branch refs/heads/activemq-5.17.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=7962ccb6f ] AMQ-9466: Upgrade to log4j 2.23.1 > Upgrade to log4j 2.23.1 > --- > > Key: AMQ-9466 > URL: https://issues.apache.org/jira/browse/AMQ-9466 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9466) Upgrade to log4j 2.23.1
[ https://issues.apache.org/jira/browse/AMQ-9466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830787#comment-17830787 ] ASF subversion and git services commented on AMQ-9466: -- Commit f1b219a1110a446d5fc22f185e9615b8f7bda051 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f1b219a11 ] AMQ-9466: Upgrade to log4j 2.23.1 (cherry picked from commit 55b5ae5ad84a5dc07d68899f54cbf915f4dd8097) > Upgrade to log4j 2.23.1 > --- > > Key: AMQ-9466 > URL: https://issues.apache.org/jira/browse/AMQ-9466 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9466) Upgrade to log4j 2.23.1
[ https://issues.apache.org/jira/browse/AMQ-9466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830785#comment-17830785 ] ASF subversion and git services commented on AMQ-9466: -- Commit 55b5ae5ad84a5dc07d68899f54cbf915f4dd8097 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=55b5ae5ad ] AMQ-9466: Upgrade to log4j 2.23.1 > Upgrade to log4j 2.23.1 > --- > > Key: AMQ-9466 > URL: https://issues.apache.org/jira/browse/AMQ-9466 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9466) Upgrade to log4j 2.23.1
[ https://issues.apache.org/jira/browse/AMQ-9466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830786#comment-17830786 ] ASF subversion and git services commented on AMQ-9466: -- Commit a611b143da8af7beb6dd2a96088332ea6bc678cd in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a611b143d ] Merge pull request #1190 from jbonofre/AMQ-9466 AMQ-9466: Upgrade to log4j 2.23.1 > Upgrade to log4j 2.23.1 > --- > > Key: AMQ-9466 > URL: https://issues.apache.org/jira/browse/AMQ-9466 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9465) Upgrade to slf4j 2.0.12
[ https://issues.apache.org/jira/browse/AMQ-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830784#comment-17830784 ] ASF subversion and git services commented on AMQ-9465: -- Commit 84814b15ca2c17f324db4ca7f14966821165eef1 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=84814b15c ] AMQ-9465: Upgrade to slf4j 2.0.12 (cherry picked from commit 9d1cd325b57a986b191ca24751a6f6cb4059fc1e) > Upgrade to slf4j 2.0.12 > --- > > Key: AMQ-9465 > URL: https://issues.apache.org/jira/browse/AMQ-9465 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9465) Upgrade to slf4j 2.0.12
[ https://issues.apache.org/jira/browse/AMQ-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830782#comment-17830782 ] ASF subversion and git services commented on AMQ-9465: -- Commit 9d1cd325b57a986b191ca24751a6f6cb4059fc1e in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=9d1cd325b ] AMQ-9465: Upgrade to slf4j 2.0.12 > Upgrade to slf4j 2.0.12 > --- > > Key: AMQ-9465 > URL: https://issues.apache.org/jira/browse/AMQ-9465 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9465) Upgrade to slf4j 2.0.12
[ https://issues.apache.org/jira/browse/AMQ-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830783#comment-17830783 ] ASF subversion and git services commented on AMQ-9465: -- Commit 3f2b2ba0aedd0d26d52b47c29d60552534ad4bfe in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=3f2b2ba0a ] Merge pull request #1189 from jbonofre/AMQ-9465 AMQ-9465: Upgrade to slf4j 2.0.12 > Upgrade to slf4j 2.0.12 > --- > > Key: AMQ-9465 > URL: https://issues.apache.org/jira/browse/AMQ-9465 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9464) Upgrade to commons-dbcp2 2.12.0
[ https://issues.apache.org/jira/browse/AMQ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830486#comment-17830486 ] ASF subversion and git services commented on AMQ-9464: -- Commit 42c770e11ba6f575034bc5bd63525c227526e035 in activemq's branch refs/heads/activemq-5.17.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=42c770e11 ] AMQ-9464: Upgrade to commons-dbcp2 2.12.0 (cherry picked from commit 98868995c250bcbe27dd5895fd7af211ec9cf1e9) > Upgrade to commons-dbcp2 2.12.0 > --- > > Key: AMQ-9464 > URL: https://issues.apache.org/jira/browse/AMQ-9464 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker, JDBC >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9464) Upgrade to commons-dbcp2 2.12.0
[ https://issues.apache.org/jira/browse/AMQ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830485#comment-17830485 ] ASF subversion and git services commented on AMQ-9464: -- Commit 72b18e193293605ddf46c23992a5f3fdcc66f1d4 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=72b18e193 ] AMQ-9464: Upgrade to commons-dbcp2 2.12.0 (cherry picked from commit 98868995c250bcbe27dd5895fd7af211ec9cf1e9) > Upgrade to commons-dbcp2 2.12.0 > --- > > Key: AMQ-9464 > URL: https://issues.apache.org/jira/browse/AMQ-9464 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker, JDBC >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9464) Upgrade to commons-dbcp2 2.12.0
[ https://issues.apache.org/jira/browse/AMQ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830482#comment-17830482 ] ASF subversion and git services commented on AMQ-9464: -- Commit 98868995c250bcbe27dd5895fd7af211ec9cf1e9 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=98868995c ] AMQ-9464: Upgrade to commons-dbcp2 2.12.0 > Upgrade to commons-dbcp2 2.12.0 > --- > > Key: AMQ-9464 > URL: https://issues.apache.org/jira/browse/AMQ-9464 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker, JDBC >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9464) Upgrade to commons-dbcp2 2.12.0
[ https://issues.apache.org/jira/browse/AMQ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830483#comment-17830483 ] ASF subversion and git services commented on AMQ-9464: -- Commit 4c633e69a778a95188166efbb12b7ea71501ae2a in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4c633e69a ] Merge pull request #1188 from jbonofre/AMQ-9464 AMQ-9464: Upgrade to commons-dbcp2 2.12.0 > Upgrade to commons-dbcp2 2.12.0 > --- > > Key: AMQ-9464 > URL: https://issues.apache.org/jira/browse/AMQ-9464 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker, JDBC >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4697) Auto reload SSL PEM config sources on change
[ https://issues.apache.org/jira/browse/ARTEMIS-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830480#comment-17830480 ] ASF subversion and git services commented on ARTEMIS-4697: -- Commit 3598177734bd00eba4e404fc1084534249ddc00e in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=3598177734 ] ARTEMIS-4697 Auto reload SSL PEM config sources on change > Auto reload SSL PEM config sources on change > > > Key: ARTEMIS-4697 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4697 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In ARTEMIS-4164 we added auto reload acceptor SSL keystores on change. It > would make sense to auto reload automatically also when a change of the PEM > config sources is detected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9462) Upgrade to Jackson 2.16.2
[ https://issues.apache.org/jira/browse/AMQ-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830406#comment-17830406 ] ASF subversion and git services commented on AMQ-9462: -- Commit 30c96ac9c2903419ef523dc33ee852013020f16e in activemq's branch refs/heads/activemq-5.17.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=30c96ac9c ] AMQ-9462: Upgrade to Jackson 2.16.2 > Upgrade to Jackson 2.16.2 > - > > Key: AMQ-9462 > URL: https://issues.apache.org/jira/browse/AMQ-9462 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9462) Upgrade to Jackson 2.16.2
[ https://issues.apache.org/jira/browse/AMQ-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830405#comment-17830405 ] ASF subversion and git services commented on AMQ-9462: -- Commit 14eacefc1966adcb207ba36ff2cf7868e1f58164 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=14eacefc1 ] AMQ-9462: Upgrade to Jackson 2.16.2 > Upgrade to Jackson 2.16.2 > - > > Key: AMQ-9462 > URL: https://issues.apache.org/jira/browse/AMQ-9462 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9462) Upgrade to Jackson 2.16.2
[ https://issues.apache.org/jira/browse/AMQ-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830403#comment-17830403 ] ASF subversion and git services commented on AMQ-9462: -- Commit f056d9572610a624dd7dd943e368331bc75348aa in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f056d9572 ] AMQ-9462: Upgrade to Jackson 2.16.2 > Upgrade to Jackson 2.16.2 > - > > Key: AMQ-9462 > URL: https://issues.apache.org/jira/browse/AMQ-9462 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9462) Upgrade to Jackson 2.16.2
[ https://issues.apache.org/jira/browse/AMQ-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830404#comment-17830404 ] ASF subversion and git services commented on AMQ-9462: -- Commit 5d940c8e179a542395e81ca4786989277af42324 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=5d940c8e1 ] Merge pull request #1186 from jbonofre/AMQ-9462 AMQ-9462: Upgrade to Jackson 2.16.2 > Upgrade to Jackson 2.16.2 > - > > Key: AMQ-9462 > URL: https://issues.apache.org/jira/browse/AMQ-9462 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9463) Upgrade to Camel 4.4.1
[ https://issues.apache.org/jira/browse/AMQ-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830283#comment-17830283 ] ASF subversion and git services commented on AMQ-9463: -- Commit 4530caa1045baba314725aa9805f80749469e7a5 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4530caa10 ] AMQ-9463: Upgrade to Camel 4.4.1 > Upgrade to Camel 4.4.1 > -- > > Key: AMQ-9463 > URL: https://issues.apache.org/jira/browse/AMQ-9463 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Camel >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9463) Upgrade to Camel 4.4.1
[ https://issues.apache.org/jira/browse/AMQ-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830284#comment-17830284 ] ASF subversion and git services commented on AMQ-9463: -- Commit eae193bc33f112a8f33acb103848693c83934437 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=eae193bc3 ] Merge pull request #1187 from jbonofre/AMQ-9463 AMQ-9463: Upgrade to Camel 4.4.1 > Upgrade to Camel 4.4.1 > -- > > Key: AMQ-9463 > URL: https://issues.apache.org/jira/browse/AMQ-9463 > Project: ActiveMQ Classic > Issue Type: Dependency upgrade > Components: Camel >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.4, 5.17.7, 6.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9452) StatisticsPlugin - field firstMessageTimestamp is not produced for AuthorizationDestinationFilter
[
https://issues.apache.org/jira/browse/AMQ-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830205#comment-17830205
]
ASF subversion and git services commented on AMQ-9452:
--
Commit 8beea0faca2c563b7a3630fab0e5ab18e5c6e4c6 in activemq's branch
refs/heads/activemq-5.17.x from Grzegorz Kochanski
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=8beea0fac ]
AMQ-9452: unwrap BaseDestination to access queue/topic message
Change-Id: Ic05002ecb428e2aa5abeb9dc3e499e3aae550051
(cherry picked from commit 4d40023968fc334982f15e9c9623b1d74d308931)
> StatisticsPlugin - field firstMessageTimestamp is not produced for
> AuthorizationDestinationFilter
> -
>
> Key: AMQ-9452
> URL: https://issues.apache.org/jira/browse/AMQ-9452
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.18.3
>Reporter: Grzegorz Kochański
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.4, 5.17.7, 6.1.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{StatisticsBroker}} does not send field {{firstMessageTimestamp}} as dest
> may be instance of {{DestinationFilter}} (in my case:
> {{{}AuthorizationDestinationFilter{}}})
> {code:java}
> if (includeFirstMessageTimestamp) {
> if (dest instanceof Queue) {
> ((Queue) dest).doBrowse(tempFirstMessage, 1);
> }
> else if (dest instanceof Topic) {
> ((Topic) dest).doBrowse(tempFirstMessage, 1);
> }
> if (!tempFirstMessage.isEmpty()) {
> Message message = tempFirstMessage.get(0);
> // NOTICE: Client-side, you may get the broker "now" Timestamp by
> msg.getJMSTimestamp()
> // This allows for calculating age.
> statsMessage.setLong("firstMessageTimestamp",
> message.getBrokerInTime());
> tempFirstMessage.clear();
> } {code}
>
> It appears that {{BaseDestination}} may be unwinded:
> {code:java}
> //unwind BaseDestination
> while (dest instanceof DestinationFilter) {
> dest = ((DestinationFilter) dest).getNext();
> }
> {code}
>
>
> related to feature:
> https://github.com/apache/activemq/commit/9167a79b79e4c121cfe0a5b82456f52bf3ecc3c7
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9452) StatisticsPlugin - field firstMessageTimestamp is not produced for AuthorizationDestinationFilter
[
https://issues.apache.org/jira/browse/AMQ-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830204#comment-17830204
]
ASF subversion and git services commented on AMQ-9452:
--
Commit 3b0a646af24cef2335f8a7c9a48332dc5bcf6bb5 in activemq's branch
refs/heads/activemq-5.18.x from Grzegorz Kochanski
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=3b0a646af ]
AMQ-9452: unwrap BaseDestination to access queue/topic message
Change-Id: Ic05002ecb428e2aa5abeb9dc3e499e3aae550051
(cherry picked from commit 4d40023968fc334982f15e9c9623b1d74d308931)
> StatisticsPlugin - field firstMessageTimestamp is not produced for
> AuthorizationDestinationFilter
> -
>
> Key: AMQ-9452
> URL: https://issues.apache.org/jira/browse/AMQ-9452
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.18.3
>Reporter: Grzegorz Kochański
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.4, 5.17.7, 6.1.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{StatisticsBroker}} does not send field {{firstMessageTimestamp}} as dest
> may be instance of {{DestinationFilter}} (in my case:
> {{{}AuthorizationDestinationFilter{}}})
> {code:java}
> if (includeFirstMessageTimestamp) {
> if (dest instanceof Queue) {
> ((Queue) dest).doBrowse(tempFirstMessage, 1);
> }
> else if (dest instanceof Topic) {
> ((Topic) dest).doBrowse(tempFirstMessage, 1);
> }
> if (!tempFirstMessage.isEmpty()) {
> Message message = tempFirstMessage.get(0);
> // NOTICE: Client-side, you may get the broker "now" Timestamp by
> msg.getJMSTimestamp()
> // This allows for calculating age.
> statsMessage.setLong("firstMessageTimestamp",
> message.getBrokerInTime());
> tempFirstMessage.clear();
> } {code}
>
> It appears that {{BaseDestination}} may be unwinded:
> {code:java}
> //unwind BaseDestination
> while (dest instanceof DestinationFilter) {
> dest = ((DestinationFilter) dest).getNext();
> }
> {code}
>
>
> related to feature:
> https://github.com/apache/activemq/commit/9167a79b79e4c121cfe0a5b82456f52bf3ecc3c7
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
