[
https://issues.jboss.org/browse/WFLY-8579?page=com.atlassian.jira.plugin....
]
Scott Van Wart commented on WFLY-8579:
--------------------------------------
I attached a maven project that builds an ear for deployment. Run wildfly with
standalone.<bat|sh> --server-config=standalone-full-ha.xml, deploy, and access
http://localhost:8080/leak-web/rest/test?message=Hi and watch the logs for each of
TestTopicListener1 and TestTopicListener2.
Topic messages are sent to all shared non-durable subscription
participants
---------------------------------------------------------------------------
Key: WFLY-8579
URL:
https://issues.jboss.org/browse/WFLY-8579
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.1.0.Final
Reporter: Scott Van Wart
Assignee: Jeff Mesnil
Attachments: duplicate-shared.zip
I have two MDBs with a subscription to a topic. The same clientId and a subscriptionName
are specified in the activation config properties for each MDB. subscriptionDurability is
omitted (defaulted to NonDurable).
When I send a single message to this topic, both MDBs receive the message. According to
JSR 343, 8.3.2 Shared non-durable subscriptions:
bq. A non-durable shared subscription is used by a client that needs to be able to
share the work of receiving messages from a non-durable topic subscription
amongst multiple consumers. A non-durable shared subscription may
therefore have more than one consumer. *Each message from the subscription will be
delivered to only one of the consumers on that
subscription.*
Setting the subscriptionDurability property to Durable works as expected (each message is
delivered to only one consumer in that subscription).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)