[jboss-jira] [JBoss JIRA] (WFLY-8579) Topic messages are sent to all shared non-durable subscription participants

[Miroslav Novak (Jira)]

    [ https://issues.jboss.org/browse/WFLY-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673536#comment-13673536 ] 

Miroslav Novak commented on WFLY-8579:
--------------------------------------

If MDBs are configured like:
{code}
@MessageDriven(name = "mdb1",
        activationConfig = {
                @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),
                @ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/topic/InTopic"),
                @ActivationConfigProperty(propertyName = "clientID", propertyValue = "testing-client-id"),
                @ActivationConfigProperty(propertyName = "subscriptionName", propertyValue = "testing-subscription-name"),
                @ActivationConfigProperty(propertyName = "shareSubscriptions", propertyValue = "true"),
                @ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Durable")})
{code}

and deployed to nodes in cluster then all are sharing the same subscription. So in case above if 200 messages are sent to InTopic then sum of all messages received by MDB across cluster is 200. 

I'll close this jira.

> 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: ehsavoie Hugonnet
>            Priority: Major
>         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.12.1#712002)