[jira] [Resolved] (AMQ-8149) Create Docker Image
[ https://issues.apache.org/jira/browse/AMQ-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-8149. --- Resolution: Fixed > Create Docker Image > --- > > Key: AMQ-8149 > URL: https://issues.apache.org/jira/browse/AMQ-8149 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Create an Apache ActiveMQ docker image > Draft: > [X] -jib- or jkube mvn plugin [Use jkube for support of multiple base images > (debian, alpine, ubi etc)] > [ ] Create a general container that supports most use cases (enable all > protocols on default ports, etc) > [ ] Provide artifacts for users to build customized containers > Tasks: > [DONE] Creation of Docker repository for ActiveMQ INFRA-21430 > [ ] Add activemq-docker module to 5.17.x (activemq-assembly) > [ ] Add dockerhub deployment to release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-8149) Create Docker Image
[ https://issues.apache.org/jira/browse/AMQ-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736657#comment-17736657 ] ASF subversion and git services commented on AMQ-8149: -- Commit 046c36a381d0f8c0920b04dcf22b2b86f2bba046 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=046c36a381 ] Merge pull request #1036 from jbonofre/AMQ-8149 [AMQ-8149] Add tooling to create activemq docker image (including multi-platform support) > Create Docker Image > --- > > Key: AMQ-8149 > URL: https://issues.apache.org/jira/browse/AMQ-8149 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Create an Apache ActiveMQ docker image > Draft: > [X] -jib- or jkube mvn plugin [Use jkube for support of multiple base images > (debian, alpine, ubi etc)] > [ ] Create a general container that supports most use cases (enable all > protocols on default ports, etc) > [ ] Provide artifacts for users to build customized containers > Tasks: > [DONE] Creation of Docker repository for ActiveMQ INFRA-21430 > [ ] Add activemq-docker module to 5.17.x (activemq-assembly) > [ ] Add dockerhub deployment to release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-8149) Create Docker Image
[ https://issues.apache.org/jira/browse/AMQ-8149?focusedWorklogId=867234&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867234 ] ASF GitHub Bot logged work on AMQ-8149: --- Author: ASF GitHub Bot Created on: 24/Jun/23 04:23 Start Date: 24/Jun/23 04:23 Worklog Time Spent: 10m Work Description: jbonofre merged PR #1036: URL: https://github.com/apache/activemq/pull/1036 Issue Time Tracking --- Worklog Id: (was: 867234) Time Spent: 20m (was: 10m) > Create Docker Image > --- > > Key: AMQ-8149 > URL: https://issues.apache.org/jira/browse/AMQ-8149 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Create an Apache ActiveMQ docker image > Draft: > [X] -jib- or jkube mvn plugin [Use jkube for support of multiple base images > (debian, alpine, ubi etc)] > [ ] Create a general container that supports most use cases (enable all > protocols on default ports, etc) > [ ] Provide artifacts for users to build customized containers > Tasks: > [DONE] Creation of Docker repository for ActiveMQ INFRA-21430 > [ ] Add activemq-docker module to 5.17.x (activemq-assembly) > [ ] Add dockerhub deployment to release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (AMQ-8150) Support multiple OS and JDK docker image combinations
[ https://issues.apache.org/jira/browse/AMQ-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-8150. --- Fix Version/s: 5.19.0 Resolution: Fixed > Support multiple OS and JDK docker image combinations > - > > Key: AMQ-8150 > URL: https://issues.apache.org/jira/browse/AMQ-8150 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.2 > > > As a follow-on to initial docker container support. Look to extend OS and JDK > combinations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9233) NPE in SubQueueSelectorCacheBroker.removeConsumer
[
https://issues.apache.org/jira/browse/AMQ-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736655#comment-17736655
]
ASF subversion and git services commented on AMQ-9233:
--
Commit 2383a06b20c4d32f2ac44271c91f7deb80bfc38c in activemq's branch
refs/heads/activemq-5.18.x from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=2383a06b20 ]
[AMQ-9233] Prevent NPE in SubQueueSelectorCacheBroker
(cherry picked from commit 95e3c2a1aa0d4962ad6a22a4422a9314875f824b)
> NPE in SubQueueSelectorCacheBroker.removeConsumer
> -
>
> Key: AMQ-9233
> URL: https://issues.apache.org/jira/browse/AMQ-9233
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.4
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.19.0, 5.18.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This NPE occurs after a number of cascading errors. Probably, the
> _selectors.size()_ needs a null check.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.activemq.plugin.SubQueueSelectorCacheBroker.removeConsumer(SubQueueSelectorCacheBroker.java:183)[activemq-broker-5.16.4.jar:5.16.4]
> at
> org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:139)[activemq-broker-5.16.4.jar:5.16.4]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-8149) Create Docker Image
[ https://issues.apache.org/jira/browse/AMQ-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736656#comment-17736656 ] ASF subversion and git services commented on AMQ-8149: -- Commit 85276d347688611672b797561de303e609ae9519 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=85276d3476 ] [AMQ-8149] Add tooling to create activemq docker image (including multi-platform support) > Create Docker Image > --- > > Key: AMQ-8149 > URL: https://issues.apache.org/jira/browse/AMQ-8149 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Create an Apache ActiveMQ docker image > Draft: > [X] -jib- or jkube mvn plugin [Use jkube for support of multiple base images > (debian, alpine, ubi etc)] > [ ] Create a general container that supports most use cases (enable all > protocols on default ports, etc) > [ ] Provide artifacts for users to build customized containers > Tasks: > [DONE] Creation of Docker repository for ActiveMQ INFRA-21430 > [ ] Add activemq-docker module to 5.17.x (activemq-assembly) > [ ] Add dockerhub deployment to release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (AMQ-9233) NPE in SubQueueSelectorCacheBroker.removeConsumer
[
https://issues.apache.org/jira/browse/AMQ-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved AMQ-9233.
---
Resolution: Fixed
> NPE in SubQueueSelectorCacheBroker.removeConsumer
> -
>
> Key: AMQ-9233
> URL: https://issues.apache.org/jira/browse/AMQ-9233
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.4
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.19.0, 5.18.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This NPE occurs after a number of cascading errors. Probably, the
> _selectors.size()_ needs a null check.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.activemq.plugin.SubQueueSelectorCacheBroker.removeConsumer(SubQueueSelectorCacheBroker.java:183)[activemq-broker-5.16.4.jar:5.16.4]
> at
> org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:139)[activemq-broker-5.16.4.jar:5.16.4]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9233) NPE in SubQueueSelectorCacheBroker.removeConsumer
[
https://issues.apache.org/jira/browse/AMQ-9233?focusedWorklogId=867233&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867233
]
ASF GitHub Bot logged work on AMQ-9233:
---
Author: ASF GitHub Bot
Created on: 24/Jun/23 04:22
Start Date: 24/Jun/23 04:22
Worklog Time Spent: 10m
Work Description: jbonofre merged PR #1034:
URL: https://github.com/apache/activemq/pull/1034
Issue Time Tracking
---
Worklog Id: (was: 867233)
Time Spent: 20m (was: 10m)
> NPE in SubQueueSelectorCacheBroker.removeConsumer
> -
>
> Key: AMQ-9233
> URL: https://issues.apache.org/jira/browse/AMQ-9233
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.4
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.19.0, 5.18.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This NPE occurs after a number of cascading errors. Probably, the
> _selectors.size()_ needs a null check.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.activemq.plugin.SubQueueSelectorCacheBroker.removeConsumer(SubQueueSelectorCacheBroker.java:183)[activemq-broker-5.16.4.jar:5.16.4]
> at
> org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:139)[activemq-broker-5.16.4.jar:5.16.4]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9233) NPE in SubQueueSelectorCacheBroker.removeConsumer
[
https://issues.apache.org/jira/browse/AMQ-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736653#comment-17736653
]
ASF subversion and git services commented on AMQ-9233:
--
Commit 95e3c2a1aa0d4962ad6a22a4422a9314875f824b in activemq's branch
refs/heads/main from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=95e3c2a1aa ]
[AMQ-9233] Prevent NPE in SubQueueSelectorCacheBroker
> NPE in SubQueueSelectorCacheBroker.removeConsumer
> -
>
> Key: AMQ-9233
> URL: https://issues.apache.org/jira/browse/AMQ-9233
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.4
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.19.0, 5.18.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This NPE occurs after a number of cascading errors. Probably, the
> _selectors.size()_ needs a null check.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.activemq.plugin.SubQueueSelectorCacheBroker.removeConsumer(SubQueueSelectorCacheBroker.java:183)[activemq-broker-5.16.4.jar:5.16.4]
> at
> org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:139)[activemq-broker-5.16.4.jar:5.16.4]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9233) NPE in SubQueueSelectorCacheBroker.removeConsumer
[
https://issues.apache.org/jira/browse/AMQ-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736654#comment-17736654
]
ASF subversion and git services commented on AMQ-9233:
--
Commit 251577cf610bbc2596ac114a1fc36daadee3147c in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=251577cf61 ]
Merge pull request #1034 from jbonofre/AMQ-9233
[AMQ-9233] Prevent NPE in SubQueueSelectorCacheBroker
> NPE in SubQueueSelectorCacheBroker.removeConsumer
> -
>
> Key: AMQ-9233
> URL: https://issues.apache.org/jira/browse/AMQ-9233
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.4
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.19.0, 5.18.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This NPE occurs after a number of cascading errors. Probably, the
> _selectors.size()_ needs a null check.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.activemq.plugin.SubQueueSelectorCacheBroker.removeConsumer(SubQueueSelectorCacheBroker.java:183)[activemq-broker-5.16.4.jar:5.16.4]
> at
> org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:139)[activemq-broker-5.16.4.jar:5.16.4]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4095) OpenWire clients are unable to consume from mutlicast queue after 2nd paging
[
https://issues.apache.org/jira/browse/ARTEMIS-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736635#comment-17736635
]
Artyom Tarasenko commented on ARTEMIS-4095:
---
Now, knowing that the problem is in the accounting of the persistentSize of the
delivering messages, it was easy to find the reason why it keeps growing:
incrementDeliverered() size in the test scenario above is always adding more
than decrementDeliverered(). It's possible to see it when sending a single
message and consume it with a XA Consumer: the persistentCount drops to 0, but
persistenSize stays >0. Comparing the refereneces for incrementing and
decrementing it turned out that the incrementing message has "__AMQ_CID"
property set, while decrement doesn't have it. Which in turn happens because
the fix for ARTEMIS-980 has a (meanwhile?) wrong assumption about the internal
sessions:
{code:java}
//internal session always delivers messages to noLocal advisory
consumers
//so we need to remove this property too.
message.removeProperty(MessageUtil.CONNECTION_ID_PROPERTY_NAME);{code}
The assumption is wrong because internal sessions are also used for handling
the XA-Transactions. The attached patch fixes the issue for me. [~jbertram]
would it be possible to include it into the next release? And since it's a
bugfix into a minor release too?
[^0001-ARTEMIS-4095-fix-delivering-message-size-accounting.patch]
> OpenWire clients are unable to consume from mutlicast queue after 2nd paging
>
>
> Key: ARTEMIS-4095
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4095
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
>Affects Versions: 2.26.0, 2.27.0, 2.27.1, 2.28.0, 2.29.0
> Environment: Artemis, deployed through the official docker image in
> version {{2.26.0}} in an OpenShift cluster
>Reporter: Marco Bungart
>Priority: Major
> Attachments:
> 0001-ARTEMIS-4095-fix-delivering-message-size-accounting.patch,
> artemis-Xmx1G.png, artemis-Xmx2G.png, graph1.png, graph2.png,
> jmeter-orders-6500-localhost.jmx, jmsconsumer-1.0-SNAPSHOT.jar
>
>
> I observed that after artemis went into paging for the 2nd time, OpenWire
> clients were not able to read messages from their corresponding addresses.
> Restarting the applications connected as clients does not fix the issue.
> Restarting artemis, however, does fix the issue.
> Both images attached show the messages of two queues.
> - The upper (orange) line in the 1st graph shows count of messages in a queue
> to which core clients are connected.
> - The lower (blue) line in the 1stg raph shows count of messages in a queue
> to which OpenWire clients are connected.
> - in the 2nd graph, the upper (violet) line shows count of messages in a
> queue to which core clients are connected.
> - in the 2nd graph, the lower (green) line shows count of messages in a queue
> to which OpenWire clients are connected.
> I have a heap dump that we could share, showing the accumulated objects. the
> dump is about 90 MB in size If this would be helpful to have, please let me
> know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4095) OpenWire clients are unable to consume from mutlicast queue after 2nd paging
[
https://issues.apache.org/jira/browse/ARTEMIS-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artyom Tarasenko updated ARTEMIS-4095:
--
Attachment: 0001-ARTEMIS-4095-fix-delivering-message-size-accounting.patch
> OpenWire clients are unable to consume from mutlicast queue after 2nd paging
>
>
> Key: ARTEMIS-4095
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4095
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
>Affects Versions: 2.26.0, 2.27.0, 2.27.1, 2.28.0, 2.29.0
> Environment: Artemis, deployed through the official docker image in
> version {{2.26.0}} in an OpenShift cluster
>Reporter: Marco Bungart
>Priority: Major
> Attachments:
> 0001-ARTEMIS-4095-fix-delivering-message-size-accounting.patch,
> artemis-Xmx1G.png, artemis-Xmx2G.png, graph1.png, graph2.png,
> jmeter-orders-6500-localhost.jmx, jmsconsumer-1.0-SNAPSHOT.jar
>
>
> I observed that after artemis went into paging for the 2nd time, OpenWire
> clients were not able to read messages from their corresponding addresses.
> Restarting the applications connected as clients does not fix the issue.
> Restarting artemis, however, does fix the issue.
> Both images attached show the messages of two queues.
> - The upper (orange) line in the 1st graph shows count of messages in a queue
> to which core clients are connected.
> - The lower (blue) line in the 1stg raph shows count of messages in a queue
> to which OpenWire clients are connected.
> - in the 2nd graph, the upper (violet) line shows count of messages in a
> queue to which core clients are connected.
> - in the 2nd graph, the lower (green) line shows count of messages in a queue
> to which OpenWire clients are connected.
> I have a heap dump that we could share, showing the accumulated objects. the
> dump is about 90 MB in size If this would be helpful to have, please let me
> know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4320) Upgrade Netty to 4.1.94.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-4320. - Fix Version/s: 2.30.0 Resolution: Fixed > Upgrade Netty to 4.1.94.Final > - > > Key: ARTEMIS-4320 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4320 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.30.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4319) Mitigate NPE in paging log statement
[
https://issues.apache.org/jira/browse/ARTEMIS-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4319.
-
Fix Version/s: 2.30.0
Resolution: Fixed
> Mitigate NPE in paging log statement
>
>
> Key: ARTEMIS-4319
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4319
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.30.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> From the user's mailing list:
> {quote}
> ...when we remove the limit, as it was too less for our case, we got null
> pointer exception in logs so we are currently forced to use less page limit.
> Since the error here tries to convert to longValue...
> {noformat}
> [org.apache.activemq.artemis.core.server] AMQ25: Sending unexpected
> exception to the client java.lang.NullPointerException: Cannot invoke
> "java.lang.Long.longValue()" because "this.pageLimitBytes" is null
> at
> org.apache.activemq.artemis.core.paging.impl.PagingStoreImpl.checkNumberOfPages(PagingStoreImpl.java:324)
> ~[artemis-server-2.28.0.jar:2.28.0]{noformat}{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4205) Allow a database to be used to meet pluggable quorum vote locking requirements
[ https://issues.apache.org/jira/browse/ARTEMIS-4205?focusedWorklogId=867203&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867203 ] ASF GitHub Bot logged work on ARTEMIS-4205: --- Author: ASF GitHub Bot Created on: 23/Jun/23 16:37 Start Date: 23/Jun/23 16:37 Worklog Time Spent: 10m Work Description: rvais commented on PR #4403: URL: https://github.com/apache/activemq-artemis/pull/4403#issuecomment-1604529631 @funkyjive would you agree that your implementation could be changed/updated to work as an implementation of potential locking mechanism for the jdbcSharedStateManager to leverage? What I, personally would like to see is simplified and unified approach. What came to my mind when reading your PR was that you could use the existing API for the locking mechanism, and just fill in your approach to locks themselves. Issue Time Tracking --- Worklog Id: (was: 867203) Time Spent: 1h 40m (was: 1.5h) > Allow a database to be used to meet pluggable quorum vote locking requirements > -- > > Key: ARTEMIS-4205 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4205 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Reporter: David Bennion >Priority: Minor > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > Utilizing the new pluggable quorum vote locking api, implement the locking > manager using a JDBC database connection. Support for Oracle, MSSQL and > Postgres is included initially, with H2 being utilized for unit testing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?focusedWorklogId=867200&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867200
]
ASF GitHub Bot logged work on ARTEMIS-4331:
---
Author: ASF GitHub Bot
Created on: 23/Jun/23 16:12
Start Date: 23/Jun/23 16:12
Worklog Time Spent: 10m
Work Description: erwindon commented on PR #4524:
URL:
https://github.com/apache/activemq-artemis/pull/4524#issuecomment-1604502831
I've updated the version designation.
Sorry, I was a bit confused about the release status as the story from
jgroups was already marked with that release number.
(and you answered the question on how to proceed, thx)
Issue Time Tracking
---
Worklog Id: (was: 867200)
Time Spent: 40m (was: 0.5h)
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?focusedWorklogId=867199&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867199
]
ASF GitHub Bot logged work on ARTEMIS-4331:
---
Author: ASF GitHub Bot
Created on: 23/Jun/23 16:11
Start Date: 23/Jun/23 16:11
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4524:
URL:
https://github.com/apache/activemq-artemis/pull/4524#issuecomment-1604501976
I'm setting this to draft until JGroups 5.2.15 is actually available.
Issue Time Tracking
---
Worklog Id: (was: 867199)
Time Spent: 0.5h (was: 20m)
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?focusedWorklogId=867194&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867194
]
ASF GitHub Bot logged work on ARTEMIS-4331:
---
Author: ASF GitHub Bot
Created on: 23/Jun/23 15:54
Start Date: 23/Jun/23 15:54
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4524:
URL:
https://github.com/apache/activemq-artemis/pull/4524#issuecomment-1604478990
Couple of things:
- JGroups 5.2.15 has not been released yet.
- Once 5.2.15 _is_ released the version designation will be `5.2.15.Final`.
Issue Time Tracking
---
Worklog Id: (was: 867194)
Time Spent: 20m (was: 10m)
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736534#comment-17736534
]
Erwin Dondorp commented on ARTEMIS-4331:
I was working on that and have added that.
But I have no way to actually test this reliably...
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?focusedWorklogId=867192&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867192
]
ASF GitHub Bot logged work on ARTEMIS-4331:
---
Author: ASF GitHub Bot
Created on: 23/Jun/23 15:41
Start Date: 23/Jun/23 15:41
Worklog Time Spent: 10m
Work Description: erwindon opened a new pull request, #4524:
URL: https://github.com/apache/activemq-artemis/pull/4524
see https://issues.apache.org/jira/browse/ARTEMIS-4331
Issue Time Tracking
---
Worklog Id: (was: 867192)
Remaining Estimate: 0h
Time Spent: 10m
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736531#comment-17736531
]
Justin Bertram commented on ARTEMIS-4331:
-
[~erwindon], do you plan on sending a PR for this?
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Deleted] (ARTEMIS-4330) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram deleted ARTEMIS-4330:
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4330
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4330
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
>Reporter: Erwin Dondorp
>Assignee: Justin Bertram
>Priority: Major
>
> I have noticed with the OWASP dependency-check plugin
> (org.owasp:dependency-check-maven:5.0.0) that the currently used
> org.jgroups:jgroups:3.6.13.Final has a [CWE-300: Channel Accessible by
> Non-Endpoint
> ('Man-in-the-Middle')|https://ossindex.sonatype.org/vuln/7c83fdab-9665-4e79-bc81-cc67fbb96417]
> vulnerability. The problem has not been reported in the NVD database,
> therefore there is no CVE record.
> The vulnerability has been
> [addressed|https://github.com/belaban/JGroups/pull/348] in version
> org.jgroups:jgroups:4.0.2.Final (at the moment the latest version is
> org.jgroups:jgroups:4.1.1.Final).
> The org.jgroups:jgroups dependency would require an upgrade to resolve the
> vulnerability.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-4331:
Issue Type: Dependency upgrade (was: Task)
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-4331:
---
Description:
I encountered a NPE in the JGROUPS facility of Artemis.
I found that it was already solved upstream in
https://issues.redhat.com/browse/JGRP-2707
hereby requesting that the updated JGroups is included in Artemis.
{noformat}
2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004: Artemis
Console available at http://0.0.0.0:8161/console
java.lang.NullPointerException
at
org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
at
org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
...
{noformat}
(first line is not part of the error message, but provided as context)
current version of jgroups is 5.2.0.Final, fix version is 5.2.15
was:
I encountered a NPE in the JGROUPS facility of Artemis.
I found that it was already solved upstream in
https://issues.redhat.com/browse/JGRP-2707
hereby requesting that the updated JGroups is included in Artemis.
{noformat}
2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004: Artemis
Console available at http://0.0.0.0:8161/console
java.lang.NullPointerException
at
org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
at
org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
...
{noformat}
(first line is not part of the error message, but provided as context)
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
> current version of jgroups is 5.2.0.Final, fix version is 5.2.15
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4331) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-4331:
---
Description:
I encountered a NPE in the JGROUPS facility of Artemis.
I found that it was already solved upstream in
https://issues.redhat.com/browse/JGRP-2707
hereby requesting that the updated JGroups is included in Artemis.
{noformat}
2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004: Artemis
Console available at http://0.0.0.0:8161/console
java.lang.NullPointerException
at
org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
at
org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
...
{noformat}
(first line is not part of the error message, but provided as context)
was:
I encountered a NPE in the JGROUPS facility of Artemis.
I found that it was already solved upstream in
https://issues.redhat.com/browse/JGRP-2707
hereby requesting that the updated JGroups is included in Artemis.
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4331
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: clustering
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Priority: Major
>
> I encountered a NPE in the JGROUPS facility of Artemis.
> I found that it was already solved upstream in
> https://issues.redhat.com/browse/JGRP-2707
> hereby requesting that the updated JGroups is included in Artemis.
> {noformat}
> 2023-06-23 14:37:59,999 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://0.0.0.0:8161/console
> java.lang.NullPointerException
> at
> org.jgroups.protocols.FD_SOCK2.getPhysicalAddresses(FD_SOCK2.java:440)
> at org.jgroups.protocols.FD_SOCK2.connectTo(FD_SOCK2.java:390)
> at
> org.jgroups.protocols.FD_SOCK2.connectToNextPingDest(FD_SOCK2.java:371)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:342)
> at org.jgroups.protocols.FD_SOCK2.handle(FD_SOCK2.java:31)
> ...
> {noformat}
> (first line is not part of the error message, but provided as context)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4331) Upgrade JGroups
Erwin Dondorp created ARTEMIS-4331: -- Summary: Upgrade JGroups Key: ARTEMIS-4331 URL: https://issues.apache.org/jira/browse/ARTEMIS-4331 Project: ActiveMQ Artemis Issue Type: Task Components: clustering Affects Versions: 2.29.0 Reporter: Erwin Dondorp I encountered a NPE in the JGROUPS facility of Artemis. I found that it was already solved upstream in https://issues.redhat.com/browse/JGRP-2707 hereby requesting that the updated JGroups is included in Artemis. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4330) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp closed ARTEMIS-4330.
--
Resolution: Invalid
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4330
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4330
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Assignee: Justin Bertram
>Priority: Major
>
> I have noticed with the OWASP dependency-check plugin
> (org.owasp:dependency-check-maven:5.0.0) that the currently used
> org.jgroups:jgroups:3.6.13.Final has a [CWE-300: Channel Accessible by
> Non-Endpoint
> ('Man-in-the-Middle')|https://ossindex.sonatype.org/vuln/7c83fdab-9665-4e79-bc81-cc67fbb96417]
> vulnerability. The problem has not been reported in the NVD database,
> therefore there is no CVE record.
> The vulnerability has been
> [addressed|https://github.com/belaban/JGroups/pull/348] in version
> org.jgroups:jgroups:4.0.2.Final (at the moment the latest version is
> org.jgroups:jgroups:4.1.1.Final).
> The org.jgroups:jgroups dependency would require an upgrade to resolve the
> vulnerability.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4330) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-4330:
---
Affects Version/s: 2.29.0
(was: 2.6.4)
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4330
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4330
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.21.0
>
>
> I have noticed with the OWASP dependency-check plugin
> (org.owasp:dependency-check-maven:5.0.0) that the currently used
> org.jgroups:jgroups:3.6.13.Final has a [CWE-300: Channel Accessible by
> Non-Endpoint
> ('Man-in-the-Middle')|https://ossindex.sonatype.org/vuln/7c83fdab-9665-4e79-bc81-cc67fbb96417]
> vulnerability. The problem has not been reported in the NVD database,
> therefore there is no CVE record.
> The vulnerability has been
> [addressed|https://github.com/belaban/JGroups/pull/348] in version
> org.jgroups:jgroups:4.0.2.Final (at the moment the latest version is
> org.jgroups:jgroups:4.1.1.Final).
> The org.jgroups:jgroups dependency would require an upgrade to resolve the
> vulnerability.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4330) Upgrade JGroups
[
https://issues.apache.org/jira/browse/ARTEMIS-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-4330:
---
Fix Version/s: (was: 2.21.0)
> Upgrade JGroups
> ---
>
> Key: ARTEMIS-4330
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4330
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
>Affects Versions: 2.29.0
>Reporter: Erwin Dondorp
>Assignee: Justin Bertram
>Priority: Major
>
> I have noticed with the OWASP dependency-check plugin
> (org.owasp:dependency-check-maven:5.0.0) that the currently used
> org.jgroups:jgroups:3.6.13.Final has a [CWE-300: Channel Accessible by
> Non-Endpoint
> ('Man-in-the-Middle')|https://ossindex.sonatype.org/vuln/7c83fdab-9665-4e79-bc81-cc67fbb96417]
> vulnerability. The problem has not been reported in the NVD database,
> therefore there is no CVE record.
> The vulnerability has been
> [addressed|https://github.com/belaban/JGroups/pull/348] in version
> org.jgroups:jgroups:4.0.2.Final (at the moment the latest version is
> org.jgroups:jgroups:4.1.1.Final).
> The org.jgroups:jgroups dependency would require an upgrade to resolve the
> vulnerability.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4330) Upgrade JGroups
Erwin Dondorp created ARTEMIS-4330:
--
Summary: Upgrade JGroups
Key: ARTEMIS-4330
URL: https://issues.apache.org/jira/browse/ARTEMIS-4330
Project: ActiveMQ Artemis
Issue Type: Dependency upgrade
Affects Versions: 2.6.4
Reporter: Erwin Dondorp
Assignee: Justin Bertram
Fix For: 2.21.0
I have noticed with the OWASP dependency-check plugin
(org.owasp:dependency-check-maven:5.0.0) that the currently used
org.jgroups:jgroups:3.6.13.Final has a [CWE-300: Channel Accessible by
Non-Endpoint
('Man-in-the-Middle')|https://ossindex.sonatype.org/vuln/7c83fdab-9665-4e79-bc81-cc67fbb96417]
vulnerability. The problem has not been reported in the NVD database,
therefore there is no CVE record.
The vulnerability has been
[addressed|https://github.com/belaban/JGroups/pull/348] in version
org.jgroups:jgroups:4.0.2.Final (at the moment the latest version is
org.jgroups:jgroups:4.1.1.Final).
The org.jgroups:jgroups dependency would require an upgrade to resolve the
vulnerability.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4328) Test can hang indefinitely
[
https://issues.apache.org/jira/browse/ARTEMIS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-4328:
Description: {{org.apache.activemq.artemis.core.server.embedded.MainTest}}
expects the broker to throw a {{java.io.IOException}} when it is started due to
its inability to find the file {{app/data/server.lock}}. However, if that files
just happens to exist then the test will simply hang indefinitely.
> Test can hang indefinitely
> --
>
> Key: ARTEMIS-4328
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4328
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{org.apache.activemq.artemis.core.server.embedded.MainTest}} expects the
> broker to throw a {{java.io.IOException}} when it is started due to its
> inability to find the file {{app/data/server.lock}}. However, if that files
> just happens to exist then the test will simply hang indefinitely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4329) dont [over]write RAT output in source tree root, use standard output location
[ https://issues.apache.org/jira/browse/ARTEMIS-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736507#comment-17736507 ] ASF subversion and git services commented on ARTEMIS-4329: -- Commit 57602a94ff93601e5711300109028547f1781818 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=57602a94ff ] ARTEMIS-4329: use standard location for RAT check output > dont [over]write RAT output in source tree root, use standard output location > - > > Key: ARTEMIS-4329 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4329 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.30.0 > > > The RAT plugin is currently configured to write output to a file at the root > of the source tree, rather than its usual location in the target dir. > This stops you being able to look at all the results (as they overwrite), its > unusual having it in the source tree rather than usual build output location, > and and also any module that fails to set the referenced activemq.basedir > property (as e.g artemis-features doesnt) then instead produces a separate > file in another part of the source tree. > Make it consistent with expectation / other projects by writing to the > standard target dir location. The output path is written on failure...and > just the check failing is usually enough anyway to see what needs fixed, > since its only going to fail upon change, and the failure inherently directs > to the module in need of a tweak to the changes being made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4329) dont [over]write RAT output in source tree root, use standard output location
[ https://issues.apache.org/jira/browse/ARTEMIS-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4329. - Resolution: Fixed > dont [over]write RAT output in source tree root, use standard output location > - > > Key: ARTEMIS-4329 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4329 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.30.0 > > > The RAT plugin is currently configured to write output to a file at the root > of the source tree, rather than its usual location in the target dir. > This stops you being able to look at all the results (as they overwrite), its > unusual having it in the source tree rather than usual build output location, > and and also any module that fails to set the referenced activemq.basedir > property (as e.g artemis-features doesnt) then instead produces a separate > file in another part of the source tree. > Make it consistent with expectation / other projects by writing to the > standard target dir location. The output path is written on failure...and > just the check failing is usually enough anyway to see what needs fixed, > since its only going to fail upon change, and the failure inherently directs > to the module in need of a tweak to the changes being made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4329) dont [over]write RAT output in source tree root, use standard output location
Robbie Gemmell created ARTEMIS-4329: --- Summary: dont [over]write RAT output in source tree root, use standard output location Key: ARTEMIS-4329 URL: https://issues.apache.org/jira/browse/ARTEMIS-4329 Project: ActiveMQ Artemis Issue Type: Task Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.30.0 The RAT plugin is currently configured to write output to a file at the root of the source tree, rather than its usual location in the target dir. This stops you being able to look at all the results (as they overwrite), its unusual having it in the source tree rather than usual build output location, and and also any module that fails to set the referenced activemq.basedir property (as e.g artemis-features doesnt) then instead produces a separate file in another part of the source tree. Make it consistent with expectation / other projects by writing to the standard target dir location. The output path is written on failure...and just the check failing is usually enough anyway to see what needs fixed, since its only going to fail upon change, and the failure inherently directs to the module in need of a tweak to the changes being made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4328) Test can hang indefinitely
[ https://issues.apache.org/jira/browse/ARTEMIS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4328: External issue URL: https://stackoverflow.com/questions/76538385/how-to-compile-activemq-artemis-with-maven > Test can hang indefinitely > -- > > Key: ARTEMIS-4328 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4328 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4328) Test can hang indefinitely
[ https://issues.apache.org/jira/browse/ARTEMIS-4328?focusedWorklogId=867172&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867172 ] ASF GitHub Bot logged work on ARTEMIS-4328: --- Author: ASF GitHub Bot Created on: 23/Jun/23 14:14 Start Date: 23/Jun/23 14:14 Worklog Time Spent: 10m Work Description: jbertram opened a new pull request, #4523: URL: https://github.com/apache/activemq-artemis/pull/4523 `org.apache.activemq.artemis.core.server.embedded.MainTest` expects the broker to throw a `java.io.IOException` when it is started due to its inability to find the file app/data/server.lock. However, if that files just happens to exist then the test will simply hang indefinitely. This commit adds a timeout to avoid hanging. Issue Time Tracking --- Worklog Id: (was: 867172) Remaining Estimate: 0h Time Spent: 10m > Test can hang indefinitely > -- > > Key: ARTEMIS-4328 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4328 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4328) Test can hang indefinitely
Justin Bertram created ARTEMIS-4328: --- Summary: Test can hang indefinitely Key: ARTEMIS-4328 URL: https://issues.apache.org/jira/browse/ARTEMIS-4328 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4325) Ability for core client to failback after failover
[ https://issues.apache.org/jira/browse/ARTEMIS-4325?focusedWorklogId=867160&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867160 ] ASF GitHub Bot logged work on ARTEMIS-4325: --- Author: ASF GitHub Bot Created on: 23/Jun/23 13:16 Start Date: 23/Jun/23 13:16 Worklog Time Spent: 10m Work Description: jbertram commented on PR #4522: URL: https://github.com/apache/activemq-artemis/pull/4522#issuecomment-1604273061 I had the same thought about using the topology update to know when the "original" node came back. I think that would be simpler than manually checking and it would save a thread as well. Issue Time Tracking --- Worklog Id: (was: 867160) Time Spent: 0.5h (was: 20m) > Ability for core client to failback after failover > -- > > Key: ARTEMIS-4325 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4325 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Anton Roskvist >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > This would be similar to the "priorityBackup" functionality in ActiveMQ > "Classic." > The primary use case for this is to more easily maintain a good distribution > of consumers and producers across a broker cluster over time. > The intended behavior for my own purposes would be something like: > * Ensure an even distribution across the broker cluster when first connecting > a high throughput client. > * When a broker becomes unavailable (network outage, patch, crash, whatever), > move affected client workers to another broker in the cluster to maintain > throughput. > * When the original broker comes back, move the recently failed-over > resources to the original broker again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4325) Ability for core client to failback after failover
[ https://issues.apache.org/jira/browse/ARTEMIS-4325?focusedWorklogId=867156&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867156 ] ASF GitHub Bot logged work on ARTEMIS-4325: --- Author: ASF GitHub Bot Created on: 23/Jun/23 12:55 Start Date: 23/Jun/23 12:55 Worklog Time Spent: 10m Work Description: brusdev commented on PR #4522: URL: https://github.com/apache/activemq-artemis/pull/4522#issuecomment-1604244307 This feature makes sense to me if your are not using HA (live/backup pairs), have you already considered waiting for a topology update to know when a node is up? https://github.com/apache/activemq-artemis/blob/main/artemis-core-client/src/main/java/org/apache/activemq/artemis/core/client/impl/ClientSessionFactoryImpl.java#L1567 Issue Time Tracking --- Worklog Id: (was: 867156) Time Spent: 20m (was: 10m) > Ability for core client to failback after failover > -- > > Key: ARTEMIS-4325 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4325 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Anton Roskvist >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > This would be similar to the "priorityBackup" functionality in ActiveMQ > "Classic." > The primary use case for this is to more easily maintain a good distribution > of consumers and producers across a broker cluster over time. > The intended behavior for my own purposes would be something like: > * Ensure an even distribution across the broker cluster when first connecting > a high throughput client. > * When a broker becomes unavailable (network outage, patch, crash, whatever), > move affected client workers to another broker in the cluster to maintain > throughput. > * When the original broker comes back, move the recently failed-over > resources to the original broker again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (AMQ-9284) Update to Proton-J 0.34.1 and Qpid JMS 1.9.0
[ https://issues.apache.org/jira/browse/AMQ-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved AMQ-9284. - Resolution: Fixed > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 > > > Key: AMQ-9284 > URL: https://issues.apache.org/jira/browse/AMQ-9284 > Project: ActiveMQ > Issue Type: Dependency upgrade > Components: AMQP >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.19.0, 5.17.5, 5.18.2 > > > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9284) Update to Proton-J 0.34.1 and Qpid JMS 1.9.0
[ https://issues.apache.org/jira/browse/AMQ-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736450#comment-17736450 ] ASF subversion and git services commented on AMQ-9284: -- Commit a73686cdc8e1ae2a69f436bf6c7cf55ad5b7c145 in activemq's branch refs/heads/activemq-5.17.x from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a73686cdc8 ] AMQ-9284: Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 (and netty 4.1.94) (cherry picked from commit d4b16aef04f58bb8ccd412e922911219603547d4) with fixups > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 > > > Key: AMQ-9284 > URL: https://issues.apache.org/jira/browse/AMQ-9284 > Project: ActiveMQ > Issue Type: Dependency upgrade > Components: AMQP >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.19.0, 5.17.5, 5.18.2 > > > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9284) Update to Proton-J 0.34.1 and Qpid JMS 1.9.0
[ https://issues.apache.org/jira/browse/AMQ-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736448#comment-17736448 ] ASF subversion and git services commented on AMQ-9284: -- Commit 9f32f98eff50d4f09cc436521b9a55e2e00fd61b in activemq's branch refs/heads/activemq-5.18.x from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=9f32f98eff ] AMQ-9284: Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 (and netty 4.1.94) (cherry picked from commit d4b16aef04f58bb8ccd412e922911219603547d4) with fixups > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 > > > Key: AMQ-9284 > URL: https://issues.apache.org/jira/browse/AMQ-9284 > Project: ActiveMQ > Issue Type: Dependency upgrade > Components: AMQP >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.19.0, 5.17.5, 5.18.2 > > > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9284) Update to Proton-J 0.34.1 and Qpid JMS 1.9.0
[ https://issues.apache.org/jira/browse/AMQ-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736444#comment-17736444 ] ASF subversion and git services commented on AMQ-9284: -- Commit d4b16aef04f58bb8ccd412e922911219603547d4 in activemq's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=d4b16aef04 ] AMQ-9284: Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 (and netty 4.1.94) > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 > > > Key: AMQ-9284 > URL: https://issues.apache.org/jira/browse/AMQ-9284 > Project: ActiveMQ > Issue Type: Dependency upgrade > Components: AMQP >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.19.0, 5.17.5, 5.18.2 > > > Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9284) Update to Proton-J 0.34.1 and Qpid JMS 1.9.0
Robbie Gemmell created AMQ-9284: --- Summary: Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 Key: AMQ-9284 URL: https://issues.apache.org/jira/browse/AMQ-9284 Project: ActiveMQ Issue Type: Dependency upgrade Components: AMQP Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 5.19.0, 5.17.5, 5.18.2 Update to Proton-J 0.34.1 and Qpid JMS 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4326) Redelivery of messages in case of LVQ queue
[
https://issues.apache.org/jira/browse/ARTEMIS-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736414#comment-17736414
]
Davide Rosso commented on ARTEMIS-4326:
---
Hi Clebert, I'll try to explain better the test scenario.
There are two source codes attached:
h2. Publisher_UC4
A java class that implements an Artemis Publisher: the publisher sends 2 kinds
of messages to the "uc4" address:
# One, and only one, message with keyid = "DUMMY" and id = 0 (where keyid is
the Last Value Key)
{code:java}
message.putStringProperty("keyid", "DUMMY");
message.putIntProperty("id", 0);
producer.send(message);
{code}
# N messages in loop, with keyid = "KEY" and id = 1 to N
{code:java}
for( int i=1; i <= messages; i ++) {
message.putStringProperty("keyid", "KEY");
message.putIntProperty("id", i);
producer.send(message);
}
{code}
Given the configuration of the address, I expect (but correct me if i'm wrong)
that a consumer connecting to the LVQ queue receives:
# The record (one) with keyid = "DUMMY" and id = 0
# The last record published with keyid = "KEY" and id =
# The following records with keyid ="KEY" and id = + X
h2. Subscriber_UC4_Core
A java class that implements an Artemis Consumer: the consumer accepts in input
the name of the queue.
In this test case the consumer connects to the LVQ queue.
{code:java}
public void onMessage(ClientMessage msg) {
try {
String body = msg.getStringBody();
int id = msg.getIntProperty("id");
String key =
msg.getStringProperty("keyid");
if (setOfIds.contains(id)) {
System.err.println("** DUPLICATE ID :" + id + " key: " + key);
} else {
System.out.println("Received msg: " + "id = " + id + " key = " + key + " body =
" + body);
setOfIds.add(id);
}
try {
Thread.sleep(10);
} catch (InterruptedException
e) {
// TODO Auto-generated
catch block
e.printStackTrace();
}
{code}
The onMessage() method keeps track of all the id's received from the queue and
signals when a duplicate key is received; a sleep of 10 millisec. then is added
to the method in order to simulate a slow consumer.
In theory, I would not expect to receive duplicates, neither for records with
keyid = "KEY", nor for the (only) record with keyid = "DUMMY".
What happens, instead, is that duplicates are received for both keyid's
> Redelivery of messages in case of LVQ queue
> ---
>
> Key: ARTEMIS-4326
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4326
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.29.0
>Reporter: Davide Rosso
>Priority: Critical
> Attachments: Publisher_UC4.java, Subscriber_UC4_Core.java
>
>
> An address configured as follows:
> {code:java}
>
>
> non-destructive="true"/>
>
>
>
>
> {code}
> One producer, one consumer (the use case actually was built to test with 2
> consumers, one reading from the LVQ queue, the other from the non-LVQ queue,
> but the issue doesn't depend on the presence of the 2nd consumer).
> * The producer sends 2 types of messages to the address "uc4"
> ** 1 message with keyid = "DUMMY" and ID = 0
> ** N messages with keyid = "KEY" and ID = 1 to 20.000
> * The consumer reads from the LVQ queue (uc4lvq); after each message, the
> consumer sleeps for 10 millisecs. to simulate a "Slow" consumer. The consumer
> keeps track of duplicate messages and writes the duplicate IDs.
> * The producer starts and begins sending messages to the address.
> * When the producer has sent 2000 messages, the consumer is started.
> I would expect the consumer to
> * Receive (once) the message with keyid = "DUMMY"
> * Receive the last message with keyid = "KEY"
> * Begin receiving the following messages.
> What happens instead is that some messages are redelivered twice; even the
> message with KEY = "DUMMY", which is the 1st message ever sent to the broker,
> is redelivered among the other more recent messages
