| Author |
Message
|
| crossland |
 Posted: Mon Feb 06, 2006 4:56 am Post subject: MQJMS3023: Subscription has an active TopicSubscriber |
 |
|
Master
Joined: 26 Jun 2001
Posts: 248
|
Since the weekend, our application has been reporting the following error:
MQJMS3023: Subscription has an active TopicSubscriber
This has continued after stopping/starting the channel and recycling the queue manager.
Has anyone managed to get round this before? |
|
| Back to top |
|
 |
| BenR |
| Posted: Mon Feb 06, 2006 6:28 am Post subject: |
|
|
Acolyte
Joined: 31 Jan 2006
Posts: 60
Location: Hursley, UK
|
| What are you trying to do when the exception is thrown? What level of MQ? And is there a linked exception? |
|
| Back to top |
|
|
| crossland |
| Posted: Mon Feb 06, 2006 6:49 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
| When the application was exiting, it tried to close the active subscriber and got MQJMS3017, Since then whenever the application restarts it gets MQJMS3023 (when it tries to subscribe). |
|
| Back to top |
|
|
| BenR |
| Posted: Mon Feb 06, 2006 7:57 am Post subject: |
|
|
Acolyte
Joined: 31 Jan 2006
Posts: 60
Location: Hursley, UK
|
More questions, sorry. When you say "it tried to close the active subscriber", do you mean topicSubscriber.close()? or something else, e.g. topicSession.unsubscribe()? Also, there should be an MQException linked to the MQJMS3017, did you capture it? That would explain why the client failed to delete the subscriber queue. And what is the subscription store property set to?
The 3023 suggests that the broker is unaware that the client closed the subscriber. Not sure why yet. |
|
| Back to top |
|
|
| crossland |
| Posted: Mon Feb 06, 2006 8:15 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
There was a reboot of the server at the weekend; we are wondering if the error was caused by an unclean shutdown.
The error was in response to MQTopicSubscriber.close. |
|
| Back to top |
|
|
| crossland |
| Posted: Thu Feb 16, 2006 6:53 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
| The call that resulted in the MQJMS3023 (Subscription has an active TopicSubscriber) was MQSubAdmin.checkInactive |
|
| Back to top |
|
|
| crossland |
| Posted: Fri Feb 17, 2006 5:58 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
Ben,
To answer your questions:
Following a reboot of Solaris, a JMS application has received error "MQJMS3023: Subscription has an active TopicSubscriber" whenever it issues MQSubAdmin.checkInactive at start up. Stopping and starting the channel has not resolved the issue; we have also tried recycling the queue manager and even rebooting the server to no avail. We also ran the cleanup utility without any success. The queue manager is using MQ Pub/Sub rather than MQSI pub/sub.
The apllication got this error when it was shutdown before the solaris reboot:
FeedException: MQJMS3017: Failed to delete subscriber queue SYSTEM.JMS.D.SUBSCRI BER.QUEUE
in response to topicSubscriber.close() |
|
| Back to top |
|
|
| chengka |
| Posted: Fri Feb 16, 2007 9:03 am Post subject: |
|
|
Newbie
Joined: 16 Feb 2007
Posts: 4
|
I would live to know what version of MQ you are using at the pub/sub broker end.
I recently moved from a 5.2 broker(ugh) to 5.3 csd10. We told the customer that the subscriber reset issue was resolved in this version and that we would not need the subscriptionreset tool. Well, this morning they sent me a note with the MQJMS3023: Subscription has an active problem, using the 5.3 server. I plan to use the CLEANUP command, but Unix has messed up java on the server, so that had to wait.
Basically, I'm very surprised that I am having his problem in v5.3 csd10. I've been misled  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Feb 17, 2007 7:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| chengka wrote: |
I would live to know what version of MQ you are using at the pub/sub broker end.
I recently moved from a 5.2 broker(ugh) to 5.3 csd10. We told the customer that the subscriber reset issue was resolved in this version and that we would not need the subscriptionreset tool. Well, this morning they sent me a note with the MQJMS3023: Subscription has an active problem, using the 5.3 server. I plan to use the CLEANUP command, but Unix has messed up java on the server, so that had to wait.
Basically, I'm very surprised that I am having his problem in v5.3 csd10. I've been misled |
If possible go to CSD 11 or better the last one (13?)
JMS was never very stable in 5.3 for CSD 08,09,10 ... especially if the client was at a different CSD version than the server...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
