** SOLVED **com.wm.app.b2b.server.jms.JMSSubsystemException: javax.jms.InvalidDestinationException


com.wm.app.b2b.server.jms.JMSSubsystemException: javax.jms.InvalidDestinationException: [BRM.10.2205] JMS: Cannot connect to queue “MY_QUEUE” with ClientGroup=JMS_BROKER. It already exists with a conflicting value.

I get the above error while enabling the JMS trigger on wM IS 7.1.2

Has anyone faced this issue before and fixed it without any fix levels.

I see SAG says to install the fix - BR_JMS_7?1_Fix2”

No…But I would say if you find resolution go a head with the fix in your lower level env?



were you able to fix this issue?

i have seen this issue if queue settings SharedState and Shared State ordering is not correct. you can refer to documentation about what values should be set.

Playing around with these values helped me fixing issue in past.

Yes we fixed this by re-creating the JMS queue and client ID on MWS:) Thanks