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

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil edited comment on WFLY-8579 at 4/14/17 6:39 AM:
------------------------------------------------------------

Note that JSR 343, 8.3.2 Shared non-durable subscriptions applies to regular JMS client, not to MDBs.

In 13.1, MDB activation properties, it is written that: 
{quote}subscriptionName - This property only applies to endpoints (message-driven beans) that receive messages published to a topic. It may be used to specify the name of the durable or non-durable subscription. It is not defined whether a shared or unshared subscription is used.
{quote}

Could you try to add the activation config property:

{code}
@ActivationConfigProperty(propertyName = "shareSubscriptions", propertyValue = "true")
{code}

to ensure that a shared subscription is used?




was (Author: jmesnil):
Note that JSR 343, 8.3.2 Shared non-durable subscriptions applies to regular JMS client, not to MDBs.

In 13.1, MDB activation properties, it is written that: 
.bq subscriptionName - This property only applies to endpoints (message-driven beans) that receive messages published to a topic. It may be used to specify the name of the durable or non-durable subscription. It is not defined whether a shared or unshared subscription is used.

Could you try to add the activation config property:

{code}
@ActivationConfigProperty(propertyName = "shareSubscriptions", propertyValue = "true")
{code}

to ensure that a shared subscription is used?



> 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)