[jira] [Commented] (ARTEMIS-4276) Message Group does not replicate properly during failover
[
https://issues.apache.org/jira/browse/ARTEMIS-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721596#comment-17721596
]
Justin Bertram commented on ARTEMIS-4276:
-
The goal of grouping messages is to ensure that the messages in the group are
processed *in order* while still allowing some level of concurrent message
consumption. Typically if you wanted to consume messages in order you'd have to
completely eliminate concurrent message consumption and restrict the number of
consumers to 1 (e.g. using an [exclusive
queue|https://activemq.apache.org/components/artemis/documentation/latest/exclusive-queues.html],
or
[{{max-consumers}}|https://activemq.apache.org/components/artemis/documentation/latest/address-model.html#shared-durable-subscription-queue-using-max-consumers]).
Using message groups allows you to have as many consumers as groups and each
group of messages can be consumed concurrently in order.
To be clear, it doesn't specifically matter than the *same* consumer gets all
the messages, only that *just one consumer at a time* gets the messages. There
is no "right consumer," per se, in this context. To this end, Artemis doesn't
guarantee that upon fail-over the same consumer will be chosen to handle the
group.
> Message Group does not replicate properly during failover
> -
>
> Key: ARTEMIS-4276
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4276
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.28.0
>Reporter: Liviu Citu
>Priority: Major
>
> Hi,
> We are currently migrating our software from Classic to Artemis and we plan
> to use failover functionality.
> We were using message group functionality by setting *JMSXGroupID* and this
> was working as expected. However after failover switch I noticed that
> messages are sent to wrong consumers.
> Our gateway/interface application is actually a collection of servers:
> * gateway adapter server: receives messages from an external systems and
> puts them on a specific/virtual topic
> * gateway loader server (can be balanced): picks up the messages from the
> topic and do processing
> * gateway fail queue: monitors all messages that failed processing and has a
> functionality of resubmitting the message (users will correct the processing
> errors and then resubmit transaction)
> *JMSXGroupID* is used to ensure that during message resubmit the same
> consumer/loader is processing the message as it was originally processed.
> However, if the message resubmit is happening during failover switch we have
> noticed that the message is not sent to the right consumer as it should.
> Basically the first available consumer is used which is not what we want.
> I have searched for configuration changes but couldn't find any relevant
> information.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4278) Incorrect Page Counters when using Prepared Transactions with Paging
[ https://issues.apache.org/jira/browse/ARTEMIS-4278?focusedWorklogId=861432=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861432 ] ASF GitHub Bot logged work on ARTEMIS-4278: --- Author: ASF GitHub Bot Created on: 10/May/23 20:55 Start Date: 10/May/23 20:55 Worklog Time Spent: 10m Work Description: clebertsuconic opened a new pull request, #4472: URL: https://github.com/apache/activemq-artemis/pull/4472 (no comment) Issue Time Tracking --- Worklog Id: (was: 861432) Remaining Estimate: 0h Time Spent: 10m > Incorrect Page Counters when using Prepared Transactions with Paging > > > Key: ARTEMIS-4278 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4278 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The system is not reloading the state on afterCommit for prepared > Transactions in relation to the page counters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4274) Push masked credential support into core client
[
https://issues.apache.org/jira/browse/ARTEMIS-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721548#comment-17721548
]
ASF subversion and git services commented on ARTEMIS-4274:
--
Commit c9c819aa885bc8ababb8f956b59aefa90d727fb7 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c9c819aa88 ]
ARTEMIS-4274 push masked credential support into core client
> Push masked credential support into core client
> ---
>
> Key: ARTEMIS-4274
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4274
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently masked credentials are only supported in the core JMS client. This
> support should be pushed down into the core client itself so things like CLI
> utilities (e.g. {{queue stat}}, {{check node}}) can use it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4274) Push masked credential support into core client
[
https://issues.apache.org/jira/browse/ARTEMIS-4274?focusedWorklogId=861433=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861433
]
ASF GitHub Bot logged work on ARTEMIS-4274:
---
Author: ASF GitHub Bot
Created on: 10/May/23 20:55
Start Date: 10/May/23 20:55
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #4470:
URL: https://github.com/apache/activemq-artemis/pull/4470
Issue Time Tracking
---
Worklog Id: (was: 861433)
Time Spent: 20m (was: 10m)
> Push masked credential support into core client
> ---
>
> Key: ARTEMIS-4274
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4274
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently masked credentials are only supported in the core JMS client. This
> support should be pushed down into the core client itself so things like CLI
> utilities (e.g. {{queue stat}}, {{check node}}) can use it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4278) Incorrect Page Counters when using Prepared Transactions with Paging
Clebert Suconic created ARTEMIS-4278: Summary: Incorrect Page Counters when using Prepared Transactions with Paging Key: ARTEMIS-4278 URL: https://issues.apache.org/jira/browse/ARTEMIS-4278 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Clebert Suconic The system is not reloading the state on afterCommit for prepared Transactions in relation to the page counters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3549) Mixed versioning of logger utitlies
[
https://issues.apache.org/jira/browse/ARTEMIS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721515#comment-17721515
]
Justin Bertram edited comment on ARTEMIS-3549 at 5/10/23 7:04 PM:
--
This is no longer valid since both the broker and the native component have
moved to SLF4J. See ARTEMIS-4020.
was (Author: jbertram):
This is no longer valid since both the broker and the native component have
moved to SLF4J.
> Mixed versioning of logger utitlies
> ---
>
> Key: ARTEMIS-3549
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3549
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: ActiveMQ-Artemis-Native
>Affects Versions: 2.19.0
>Reporter: Greg Turnquist
>Assignee: Clebert Suconic
>Priority: Minor
>
> While building Spring Web Services against Artemis Jakarta JMS 2.19.0, I ran
> into a conflict of JBoss Logger versions between various components of
> Artemis.
> Clause added to my pom.xml:
> {code:java}
>
> org.apache.activemq
> artemis-jakarta-server
> 2.19.0
> test
>
>
> jakarta.jms
> jakarta.jms-api
>
>
>
> {code}
> This resulted in two different versions of JBoss Logger getting pulled in via
> various transitive dependencies:
> {code}
> +-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
> +-org.apache.activemq:artemis-jakarta-server:2.19.0
> +-org.apache.activemq:artemis-server:2.19.0
> +-org.apache.activemq:artemis-jdbc-store:2.19.0
> +-org.jboss.logging:jboss-logging:3.4.2.Final
> and
> +-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
> +-org.apache.activemq:artemis-jakarta-server:2.19.0
> +-org.apache.activemq:artemis-server:2.19.0
> +-org.apache.activemq:activemq-artemis-native:1.0.2
> +-org.jboss.logging:jboss-logging:3.3.1.Final
> {code}
> Since I only have a single dependency, there is no way to exclude something
> in a given transitive, thus my only choice is to disable
> maven-enforcer-plugin's dependency convergence check.
> If the ActiveMQ Artemis Native module could be aligned to work with the same
> version of JBoss Logging as all the other modules, that would make it
> possible to avoid this mismatch of versions.
> NOTE: If you happen to use Maven, applying maven-enforcer-plugin to your own
> base may simplify spotting such errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-3549) Mixed versioning of logger utitlies
[
https://issues.apache.org/jira/browse/ARTEMIS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-3549.
-
Resolution: Invalid
This is no longer valid since both the broker and the native component have
moved to SLF4J.
> Mixed versioning of logger utitlies
> ---
>
> Key: ARTEMIS-3549
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3549
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: ActiveMQ-Artemis-Native
>Affects Versions: 2.19.0
>Reporter: Greg Turnquist
>Assignee: Clebert Suconic
>Priority: Minor
>
> While building Spring Web Services against Artemis Jakarta JMS 2.19.0, I ran
> into a conflict of JBoss Logger versions between various components of
> Artemis.
> Clause added to my pom.xml:
> {code:java}
>
> org.apache.activemq
> artemis-jakarta-server
> 2.19.0
> test
>
>
> jakarta.jms
> jakarta.jms-api
>
>
>
> {code}
> This resulted in two different versions of JBoss Logger getting pulled in via
> various transitive dependencies:
> {code}
> +-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
> +-org.apache.activemq:artemis-jakarta-server:2.19.0
> +-org.apache.activemq:artemis-server:2.19.0
> +-org.apache.activemq:artemis-jdbc-store:2.19.0
> +-org.jboss.logging:jboss-logging:3.4.2.Final
> and
> +-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
> +-org.apache.activemq:artemis-jakarta-server:2.19.0
> +-org.apache.activemq:artemis-server:2.19.0
> +-org.apache.activemq:activemq-artemis-native:1.0.2
> +-org.jboss.logging:jboss-logging:3.3.1.Final
> {code}
> Since I only have a single dependency, there is no way to exclude something
> in a given transitive, thus my only choice is to disable
> maven-enforcer-plugin's dependency convergence check.
> If the ActiveMQ Artemis Native module could be aligned to work with the same
> version of JBoss Logging as all the other modules, that would make it
> possible to avoid this mismatch of versions.
> NOTE: If you happen to use Maven, applying maven-enforcer-plugin to your own
> base may simplify spotting such errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3549) Mixed versioning of logger utitlies
[
https://issues.apache.org/jira/browse/ARTEMIS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721514#comment-17721514
]
Greg Turnquist commented on ARTEMIS-3549:
-
In light of [https://github.com/apache/activemq-artemis/blob/main/pom.xml#L84,]
is this ticket no longer relevant?
> Mixed versioning of logger utitlies
> ---
>
> Key: ARTEMIS-3549
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3549
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: ActiveMQ-Artemis-Native
>Affects Versions: 2.19.0
>Reporter: Greg Turnquist
>Assignee: Clebert Suconic
>Priority: Minor
>
> While building Spring Web Services against Artemis Jakarta JMS 2.19.0, I ran
> into a conflict of JBoss Logger versions between various components of
> Artemis.
> Clause added to my pom.xml:
> {code:java}
>
> org.apache.activemq
> artemis-jakarta-server
> 2.19.0
> test
>
>
> jakarta.jms
> jakarta.jms-api
>
>
>
> {code}
> This resulted in two different versions of JBoss Logger getting pulled in via
> various transitive dependencies:
> {code}
> +-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
> +-org.apache.activemq:artemis-jakarta-server:2.19.0
> +-org.apache.activemq:artemis-server:2.19.0
> +-org.apache.activemq:artemis-jdbc-store:2.19.0
> +-org.jboss.logging:jboss-logging:3.4.2.Final
> and
> +-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
> +-org.apache.activemq:artemis-jakarta-server:2.19.0
> +-org.apache.activemq:artemis-server:2.19.0
> +-org.apache.activemq:activemq-artemis-native:1.0.2
> +-org.jboss.logging:jboss-logging:3.3.1.Final
> {code}
> Since I only have a single dependency, there is no way to exclude something
> in a given transitive, thus my only choice is to disable
> maven-enforcer-plugin's dependency convergence check.
> If the ActiveMQ Artemis Native module could be aligned to work with the same
> version of JBoss Logging as all the other modules, that would make it
> possible to avoid this mismatch of versions.
> NOTE: If you happen to use Maven, applying maven-enforcer-plugin to your own
> base may simplify spotting such errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4275) _AMQ_ConsumerName is missing from Consumer Created/Closed notifications
[ https://issues.apache.org/jira/browse/ARTEMIS-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721478#comment-17721478 ] Liviu Citu commented on ARTEMIS-4275: - I totally agree with that statement. Our software is using intensively *JMS* *ActiveMQ Broker* and we want to migrate to *Artemis Broker* to benefit of the new features. We will be using Notification Messages as a replacement for Advisory Messages. Thank you for the change! > _AMQ_ConsumerName is missing from Consumer Created/Closed notifications > --- > > Key: ARTEMIS-4275 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4275 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.28.0 >Reporter: Liviu Citu >Priority: Major > > Hi, > *_AMQ_ConsumerName* property is missing from *CONSUMER_CREATED / > CONSUMER_CLOSED* notification messages. This property is necessary to > identify the *ConsumerId.* In a subscription model functionality the server > needs to know when a certain subscription (consumer) gets created or closed. > I have tried to use *_AMQ_RoutingName* but it seems it is for different > purposes (sometimes it is simply equal with *_AMQ_Address).* > *_AMQ_ConsumerName* was available in the Advisory Message but it does not > seem to be part of the Notification Message. Therefore this is a regression > compared to Classic ActiveMQ. > Regards > Liviu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4275) _AMQ_ConsumerName is missing from Consumer Created/Closed notifications
[
https://issues.apache.org/jira/browse/ARTEMIS-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721474#comment-17721474
]
Justin Bertram commented on ARTEMIS-4275:
-
To be clear, I plan on adding {{_AMQ_ConsumerName}} to the {{CONSUMER_CREATED}}
/ {{CONSUMER_CLOSED}} notification messages, but I want to reiterate [the
documentation|https://activemq.apache.org/activemq-artemis-roadmap] which
states:
bq. Artemis is not meant to be a 100% complete reimplementation of ActiveMQ
“Classic”. Features should only be reimplemented where it makes good sense.
In my opinion, this is a use-case where it makes good sense to implement
equivalent behavior.
> _AMQ_ConsumerName is missing from Consumer Created/Closed notifications
> ---
>
> Key: ARTEMIS-4275
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4275
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.28.0
>Reporter: Liviu Citu
>Priority: Major
>
> Hi,
> *_AMQ_ConsumerName* property is missing from *CONSUMER_CREATED /
> CONSUMER_CLOSED* notification messages. This property is necessary to
> identify the *ConsumerId.* In a subscription model functionality the server
> needs to know when a certain subscription (consumer) gets created or closed.
> I have tried to use *_AMQ_RoutingName* but it seems it is for different
> purposes (sometimes it is simply equal with *_AMQ_Address).*
> *_AMQ_ConsumerName* was available in the Advisory Message but it does not
> seem to be part of the Notification Message. Therefore this is a regression
> compared to Classic ActiveMQ.
> Regards
> Liviu
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4277) Upgrade checkstyle
Justin Bertram created ARTEMIS-4277: --- Summary: Upgrade checkstyle Key: ARTEMIS-4277 URL: https://issues.apache.org/jira/browse/ARTEMIS-4277 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9257) Disabled expire message checking when pauseDispatch=true
[ https://issues.apache.org/jira/browse/AMQ-9257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-9257: Fix Version/s: 5.19.0 5.17.5 5.18.2 > Disabled expire message checking when pauseDispatch=true > > > Key: AMQ-9257 > URL: https://issues.apache.org/jira/browse/AMQ-9257 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.19.0, 5.17.5, 5.18.2 > > Time Spent: 10m > Remaining Estimate: 0h > > If pauseDispatch is set, the expiry checking should be ignored as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9257) Disabled expire message checking when pauseDispatch=true
[ https://issues.apache.org/jira/browse/AMQ-9257?focusedWorklogId=861384=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861384 ] ASF GitHub Bot logged work on AMQ-9257: --- Author: ASF GitHub Bot Created on: 10/May/23 15:25 Start Date: 10/May/23 15:25 Worklog Time Spent: 10m Work Description: mattrpav opened a new pull request, #1005: URL: https://github.com/apache/activemq/pull/1005 (no comment) Issue Time Tracking --- Worklog Id: (was: 861384) Remaining Estimate: 0h Time Spent: 10m > Disabled expire message checking when pauseDispatch=true > > > Key: AMQ-9257 > URL: https://issues.apache.org/jira/browse/AMQ-9257 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > If pauseDispatch is set, the expiry checking should be ignored as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4276) Message Group does not replicate properly during failover
Liviu Citu created ARTEMIS-4276: --- Summary: Message Group does not replicate properly during failover Key: ARTEMIS-4276 URL: https://issues.apache.org/jira/browse/ARTEMIS-4276 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.28.0 Reporter: Liviu Citu Hi, We are currently migrating our software from Classic to Artemis and we plan to use failover functionality. We were using message group functionality by setting *JMSXGroupID* and this was working as expected. However after failover switch I noticed that messages are sent to wrong consumers. Our gateway/interface application is actually a collection of servers: * gateway adapter server: receives messages from an external systems and puts them on a specific/virtual topic * gateway loader server (can be balanced): picks up the messages from the topic and do processing * gateway fail queue: monitors all messages that failed processing and has a functionality of resubmitting the message (users will correct the processing errors and then resubmit transaction) *JMSXGroupID* is used to ensure that during message resubmit the same consumer/loader is processing the message as it was originally processed. However, if the message resubmit is happening during failover switch we have noticed that the message is not sent to the right consumer as it should. Basically the first available consumer is used which is not what we want. I have searched for configuration changes but couldn't find any relevant information. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-9257) Disabled expire message checking when pauseDispatch=true
[ https://issues.apache.org/jira/browse/AMQ-9257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-9257: --- Assignee: Matt Pavlovich > Disabled expire message checking when pauseDispatch=true > > > Key: AMQ-9257 > URL: https://issues.apache.org/jira/browse/AMQ-9257 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > > If pauseDispatch is set, the expiry checking should be ignored as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9257) Disabled expire message checking when pauseDispatch=true
Matt Pavlovich created AMQ-9257: --- Summary: Disabled expire message checking when pauseDispatch=true Key: AMQ-9257 URL: https://issues.apache.org/jira/browse/AMQ-9257 Project: ActiveMQ Issue Type: Improvement Reporter: Matt Pavlovich If pauseDispatch is set, the expiry checking should be ignored as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4275) _AMQ_ConsumerName is missing from Consumer Created/Closed notifications
[ https://issues.apache.org/jira/browse/ARTEMIS-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liviu Citu updated ARTEMIS-4275: Description: Hi, *_AMQ_ConsumerName* property is missing from *CONSUMER_CREATED / CONSUMER_CLOSED* notification messages. This property is necessary to identify the *ConsumerId.* In a subscription model functionality the server needs to know when a certain subscription (consumer) gets created or closed. I have tried to use *_AMQ_RoutingName* but it seems it is for different purposes (sometimes it is simply equal with *_AMQ_Address).* *_AMQ_ConsumerName* was available in the Advisory Message but it does not seem to be part of the Notification Message. Therefore this is a regression compared to Classic ActiveMQ. Regards Liviu was: Hi, *_AMQ_ConsumerName* property is missing from *CONSUMER_CREATED / CONSUMER_CLOSED* notification messages. This property is necessary to identify to identify the *ConsumerId.* In a subscription model functionality the server needs to know when a certain subscription (consumer) gets created or closed. I have tried to use *_AMQ_RoutingName* but it seems it is for different purposes (sometimes it is simply equal with *_AMQ_Address).* *_AMQ_ConsumerName* was available in the Advisory Message but it does not seem to be part of the Notification Message. Therefore this is a regression compared to Classic ActiveMQ. Regards Liviu > _AMQ_ConsumerName is missing from Consumer Created/Closed notifications > --- > > Key: ARTEMIS-4275 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4275 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.28.0 >Reporter: Liviu Citu >Priority: Major > > Hi, > *_AMQ_ConsumerName* property is missing from *CONSUMER_CREATED / > CONSUMER_CLOSED* notification messages. This property is necessary to > identify the *ConsumerId.* In a subscription model functionality the server > needs to know when a certain subscription (consumer) gets created or closed. > I have tried to use *_AMQ_RoutingName* but it seems it is for different > purposes (sometimes it is simply equal with *_AMQ_Address).* > *_AMQ_ConsumerName* was available in the Advisory Message but it does not > seem to be part of the Notification Message. Therefore this is a regression > compared to Classic ActiveMQ. > Regards > Liviu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-2824) _AMQ_Client_ID on SESSION_CLOSED notification is always null
[ https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721374#comment-17721374 ] Liviu Citu commented on ARTEMIS-2824: - I have logged: ARTEMIS-4275 > _AMQ_Client_ID on SESSION_CLOSED notification is always null > > > Key: ARTEMIS-2824 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2824 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.11.0 >Reporter: Tim Daly >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When a JMS client with a clientId set closes the session a notification > (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID > is always set to null. The JMS Client Id has been verified as being set via > the web UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4275) _AMQ_ConsumerName is missing from Consumer Created/Closed notifications
Liviu Citu created ARTEMIS-4275: --- Summary: _AMQ_ConsumerName is missing from Consumer Created/Closed notifications Key: ARTEMIS-4275 URL: https://issues.apache.org/jira/browse/ARTEMIS-4275 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.28.0 Reporter: Liviu Citu Hi, *_AMQ_ConsumerName* property is missing from *CONSUMER_CREATED / CONSUMER_CLOSED* notification messages. This property is necessary to identify to identify the *ConsumerId.* In a subscription model functionality the server needs to know when a certain subscription (consumer) gets created or closed. I have tried to use *_AMQ_RoutingName* but it seems it is for different purposes (sometimes it is simply equal with *_AMQ_Address).* *_AMQ_ConsumerName* was available in the Advisory Message but it does not seem to be part of the Notification Message. Therefore this is a regression compared to Classic ActiveMQ. Regards Liviu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-2824) _AMQ_Client_ID on SESSION_CLOSED notification is always null
[ https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721294#comment-17721294 ] Liviu Citu edited comment on ARTEMIS-2824 at 5/10/23 11:02 AM: --- Hi Justin, *_AMQ_ConsumerName* property is also missing from *CONSUMER_CREATED / CONSUMER_CLOSED* notification messages. Is it possible to set it? I need this property to identify the *ConsumerId.* We are using a subscription model functionality and on one of our servers we need to know when a certain subscription (consumer) gets created or closed. I have tried to use *_AMQ_RoutingName* but it seems it is for different purposes (in some cases when temporary queues are involved it seems to be the same as *_AMQ_Address).* *_AMQ_ConsumerName* was available in the Advisory Message but it does not seem to be part of the Notification Message. Please let me know if I should log a separate issues for it. Thank you! was (Author: JIRAUSER300236): Hi Justin, *_AMQ_ConsumerName* property is also missing from *CONSUMER_CREATED / CONSUMER_CLOSED* notification messages. Is it possible to set it? I need this property to identify the *ConsumerId.* We are using a subscription model functionality and on one of our servers we need to know when a certain subscription (consumer of a specific topic) gets created or closed. This property was available in the Advisory Message but it does not seem to be part of the Notification Message. Please let me know if I should log a separate issues for it. Thank you! > _AMQ_Client_ID on SESSION_CLOSED notification is always null > > > Key: ARTEMIS-2824 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2824 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.11.0 >Reporter: Tim Daly >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When a JMS client with a clientId set closes the session a notification > (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID > is always set to null. The JMS Client Id has been verified as being set via > the web UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-2824) _AMQ_Client_ID on SESSION_CLOSED notification is always null
[ https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721294#comment-17721294 ] Liviu Citu edited comment on ARTEMIS-2824 at 5/10/23 10:58 AM: --- Hi Justin, *_AMQ_ConsumerName* property is also missing from *CONSUMER_CREATED / CONSUMER_CLOSED* notification messages. Is it possible to set it? I need this property to identify the *ConsumerId.* We are using a subscription model functionality and on one of our servers we need to know when a certain subscription (consumer of a specific topic) gets created or closed. This property was available in the Advisory Message but it does not seem to be part of the Notification Message. Please let me know if I should log a separate issues for it. Thank you! was (Author: JIRAUSER300236): Hi Justin, *_AMQ_ConsumerName* property is also missing from *CONSUMER_CREATED / CONSUMER_CLOSED* notification messages. Is it possible to set it? I need this property to identify the *ConsumerId.* We are using a subscription model functionality and on the server side we need to know when a certain consumer (subscription) gets created or closed. This property was available in the Advisory Message but it does not seem to be part of the Notification Message. Please let me know if I should log a separate issues for it. Thank you! > _AMQ_Client_ID on SESSION_CLOSED notification is always null > > > Key: ARTEMIS-2824 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2824 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.11.0 >Reporter: Tim Daly >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When a JMS client with a clientId set closes the session a notification > (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID > is always set to null. The JMS Client Id has been verified as being set via > the web UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-2824) _AMQ_Client_ID on SESSION_CLOSED notification is always null
[
https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721294#comment-17721294
]
Liviu Citu edited comment on ARTEMIS-2824 at 5/10/23 10:57 AM:
---
Hi Justin,
*_AMQ_ConsumerName* property is also missing from *CONSUMER_CREATED /
CONSUMER_CLOSED* notification messages. Is it possible to set it? I need this
property to identify the *ConsumerId.* We are using a subscription model
functionality and on the server side we need to know when a certain consumer
(subscription) gets created or closed.
This property was available in the Advisory Message but it does not seem to be
part of the Notification Message.
Please let me know if I should log a separate issues for it.
Thank you!
was (Author: JIRAUSER300236):
Hi Justin,
*_AMQ_ConsumerName* property is also missing from *CONSUMER_CREATED /
CONSUMER_CLOSED* notification messages. Is it possible to set it? I need this
property to identify the {*}ConsumerId{*}. This property was available in the
Advisory Message but it does not seem to be part of the Notification Message.
Please let me know if I should log a separate issues for it.
Thank you!
> _AMQ_Client_ID on SESSION_CLOSED notification is always null
>
>
> Key: ARTEMIS-2824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2824
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.11.0
>Reporter: Tim Daly
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a JMS client with a clientId set closes the session a notification
> (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID
> is always set to null. The JMS Client Id has been verified as being set via
> the web UI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-2824) _AMQ_Client_ID on SESSION_CLOSED notification is always null
[
https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721294#comment-17721294
]
Liviu Citu commented on ARTEMIS-2824:
-
Hi Justin,
*_AMQ_ConsumerName* property is also missing from *CONSUMER_CREATED /
CONSUMER_CLOSED* notification messages. Is it possible to set it? I need this
property to identify the {*}ConsumerId{*}. This property was available in the
Advisory Message but it does not seem to be part of the Notification Message.
Please let me know if I should log a separate issues for it.
Thank you!
> _AMQ_Client_ID on SESSION_CLOSED notification is always null
>
>
> Key: ARTEMIS-2824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2824
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.11.0
>Reporter: Tim Daly
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a JMS client with a clientId set closes the session a notification
> (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID
> is always set to null. The JMS Client Id has been verified as being set via
> the web UI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
