| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue with multiple durable subsciber |
« View previous topic :: View next topic » |
| Author |
Message
|
| xelir13 |
 Posted: Tue Jun 25, 2013 3:11 am Post subject: Issue with multiple durable subsciber |
 |
|
Novice
Joined: 03 Feb 2013
Posts: 14
|
Currently I'm experiencing issues with the clonesupp for multiple subscriptions on our MQ environment.
The subscriber is Webmethods IS.
On normal operation days. There are multiple subscriber from the Webmethods on a Durable MQ Topic.(Our wM IS environment has 4nodes that are subscribe to the same durable topic)
Suddenly one of the nodes encountered an error stating:
Unable to start JMS Trigger MIMEngine.RECEIVE:FIXWebMethods: com.wm.app.b2b.server.jms.JMSSubsystemException: com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2011: Failed to open durable subscription '{SubscriptionName}' for destination '{Topic}'.
The whole log from the Webmethods IS states
[178891]Use a different subscription name for this durable subscriber, or run this subscriber in another JVM.
[178890]Jms attempted to create a durable subscription, but the chosen subscription name was already in use within the JVM.
[178889]2013-06-25 18:56:03 EST [ISS.0134.0053E] Unable to start JMS Trigger MIMEngine.RECEIVE:FIXWebMethods: com.wm.app.b2b.server.jms.JMSSubsystemException: com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2011: Failed to open durable subscription '{SubscriptionName}' for destination '{Topic}'.
[178888]Make sure any message consumers using this subscription are closed before trying to create a new subscription under the same name. Please see the linked exception for more information.
[178887]There may have been a problem creating the subscription due to it being used by another message consumer.
[178886]2013-06-25 18:56:03 EST [ISS.0134.0058E] JMS Trigger MIMEngine.RECEIVE:FIXWebMethods is shutting down because of exception: com.wm.app.b2b.server.jms.ResourceUnavailableException: com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0026: Failed to subscribe to topic '{Topic}' using MQSUB.
I just want to clarify if this issue is for WMQ or on Webmethods IS
Currently are workaround for this is to bounce the affected wM node. |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Tue Jun 25, 2013 3:48 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| Make sure any message consumers using this subscription are closed before trying to create a new subscription under the same name. Please see the linked exception for more information. |
Looks like a message produced by WebMethods, not MQ.
| Quote: |
| [178886]2013-06-25 18:56:03 EST [ISS.0134.0058E] JMS Trigger MIMEngine.RECEIVE:FIXWebMethods is shutting down because of exception: com.wm.app.b2b.server.jms.ResourceUnavailableException: com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0026: Failed to subscribe to topic '{Topic}' using MQSUB. |
Was that WebMethods error message followed with the MQ Reason Code, or a proper MQ linked exception ? That would indicate if MQ did not like the call to MQSUB, or WebMethods was choking on something before calling MQSUB.
_________________
Glenn |
|
| Back to top |
|
|
| xelir13 |
| Posted: Tue Jun 25, 2013 7:56 pm Post subject: Post subject: Issue with multiple durable subsciber |
|
|
Novice
Joined: 03 Feb 2013
Posts: 14
|
The wM doesn't have any MQ Reason code on their side.
I was thinking that wM is suddenly disconnecting then MQ still does recognize that wM is still connected from the same JVM that is why it cannot create another subscription unless it's bounce. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 26, 2013 5:31 am Post subject: Re: Post subject: Issue with multiple durable subsciber |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| xelir13 wrote: |
The wM doesn't have any MQ Reason code on their side.
I was thinking that wM is suddenly disconnecting then MQ still does recognize that wM is still connected from the same JVM that is why it cannot create another subscription unless it's bounce. |
A durable subscription should not need to be recreated each and every time a subscriber application starts up. The whole point of a durable subscription is that it stays around while the application itself is disconnected and disabled.
It's possible that wM has implemented some logic that always tries to create durable subscriptions at startup, and uses this failure (that the sub already exists) to find out if it's okay to proceed, or otherwise fails to suppress this error. The intent behind this choice would be to make sure the application always knew the subscription existed.
It's also possible that it's not wM that is doing this, but app specific code running in wM.
As mentioned, the MQ JMS provider includes an MQRC in a Linked Exception structure with every JMSException it throws. So wM should be reporting that somewhere.
I'd suggest you discuss this error message with the application team to find out if they are always creating their durable subscription everytime their app gets initialized, just to be sure. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
