Hmm, why not using another queue/topic or selector?
Le 5 févr. 2017 10:32, "Dignesh" <[email protected]> a écrit : > Below is the activation property element configured in my ejb-jar.xml file. > > <activation-config> > <activation-config-property> > > <activation-config-property-name>destination</activation- > config-property-name> > > <activation-config-property-value>MyTopic</activation- > config-property-value> > </activation-config-property> > <activation-config-property> > > <activation-config-property-name>destinationType</ > activation-config-property-name> > > <activation-config-property-value>javax.jms.Topic</ > activation-config-property-value> > </activation-config-property> > <activation-config-property> > > <activation-config-property-name>clientId</activation- > config-property-name> > > <activation-config-property-value>MyTopicMDB</activation- > config-property-value> > </activation-config-property> > <activation-config-property> > > <activation-config-property-name>subscriptionName</ > activation-config-property-name> > > <activation-config-property-value>MyTopicMDB_Scub</ > activation-config-property-value> > </activation-config-property> > </activation-config> > > In cluster environment having 3 nodes, Each MDB deployed creates a single > JMS connection. This is due to the unique deployement id(ClientID) we > assign > to the bean. > > Now my issue here is when I raise a JMS message, all the mdbs (Topic) in > each nodes gets the message. I need to restrict the message to be delivered > to single node. > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/Deploy-MDB-topic-in-non-clustered-way-tp4681016p4681018.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
