| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dropped ND Subscribitions |
« View previous topic :: View next topic » |
| Author |
Message
|
| jrjoe |
 Posted: Mon Jan 20, 2003 6:11 am Post subject: Dropped ND Subscribitions |
 |
|
Acolyte
Joined: 20 Jan 2003
Posts: 60
|
I was wondering if anyone has had problems with the MQ broker (support pac MA0C) losing Non-Durable Subscribtions? We have 1 publisher and 5 to 10 subscribers and it seems that once in awhile the subscriptions are lost.
Single JMS publisher, multiple non-durable JMS subscribers. Publisher running on Solaris box, JMS subscribers running on WinTel boxes.
Symptoms are periodic loss of all messages on a subscriber (other subscribers will continue to receive messages). Attempt to recover using Session.recover() method w/o success. If we close the subscription we get this exception:
Subscription close error: MQJMS3013: Failed to store admin. entry
com.ibm.mq.MQException: Completion Code 2, Reason 2033
javax.jms.JMSException: MQJMS3013: Failed to store admin. entry
at com.ibm.mq.jms.services.ConfigEnvironment.newException
(ConfigEnvironment.java:418)
at com.ibm.mq.jms.MQSubAdmin.removeND(MQSubAdmin.java:1045)
at com.ibm.mq.jms.MQTopicSubscriber.close(MQTopicSubscriber.java:452)
at
.
.
Re-subscribing (using current Session) will result in resumption of messages (unknown at this time if messages missed during this time).
I know that the 2033 means No more messages but other subscribers are still receving messages.
Any ideas ?
Thanks in advance for any help regarding this |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Mon Jan 20, 2003 6:37 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Are you geting the linked exception?
That might give the underlying MQ reason code. |
|
| Back to top |
|
|
| jrjoe |
| Posted: Mon Jan 20, 2003 7:13 am Post subject: |
|
|
Acolyte
Joined: 20 Jan 2003
Posts: 60
|
The following is the linked exception:
Subscription close error: MQJMS3013: Failed to store admin. entry
com.ibm.mq.MQException: Completion Code 2, Reason 2033
The underlying reason code is that there are no more messages on the queue. But re-subscribing using current Session will result in resumption of messages but unknown if messages missed during this time. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Mon Jan 20, 2003 7:39 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Sorry missed the 2033 first time.
Not sure what to suggest other than check that the relevant queues are defined OK, e.g.
SYSTEM.JMS.PS.STATUS.QUEUE
SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
SYSTEM.JMS.D.SUBSCRIBER.QUEUE
Also, check that no errant apps are removing msgs from these queues.
You indicate the subscribers might be using different queue managers. If so, are there any definition differences? |
|
| Back to top |
|
|
| clindsey |
| Posted: Mon Jan 20, 2003 10:38 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Could it be that the ones that are dropping could be submitted with a timeout value on the subscription while the others have an indefinite timeout on the subscription?
Just a thought,
Charlie |
|
| 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
|
|
|
|
