| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Method close() hanging |
« View previous topic :: View next topic » |
| Author |
Message
|
| Tchule |
 Posted: Mon May 27, 2002 7:02 am Post subject: Method close() hanging |
 |
|
Newbie
Joined: 27 May 2002
Posts: 2
|
Hello,
I have a problem while closing MQ objects like a QueueReceiver or a QueueSession, the close() method is hanging and never return.
My application (running in a weblogic server) is using 'permanent' listeners.
These listeners are occasionnaly disconnected from the queue manager (because of TCP/IP or because of a queue manager restart) and are becomming 'deaf'.
I try to correct the problem by restarting my listeners but the close method is blocking when i'm disconnected.
Is there a easy way to detect the fact that i'm disconnect before to try to close my objects ?
Tchule.
ps : if my english is not perfect ... it's because i'm french, please forgive me  |
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Mon May 27, 2002 11:15 am Post subject: Re: Method close() hanging |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| Tchule wrote: |
Hello,
I have a problem while closing MQ objects like a QueueReceiver or a QueueSession, the close() method is hanging and never return.
My application (running in a weblogic server) is using 'permanent' listeners.
These listeners are occasionnaly disconnected from the queue manager (because of TCP/IP or because of a queue manager restart) and are becomming 'deaf'.
I try to correct the problem by restarting my listeners but the close method is blocking when i'm disconnected.
Is there a easy way to detect the fact that i'm disconnect before to try to close my objects ?
Tchule.
ps : if my english is not perfect ... it's because i'm french, please forgive me |
Bon jour!
Please take a look at the MQSeries using Java (or any other JMS documentation) documentation for something called ExceptionListener. The method registered with such a listener will be invoked when exceptions occur in the transport (provider) layer of the JMS classes. If you don't have one of these registered, you will never get informed about MQ exceptions that happen after a successful connection has been established due to the asynchronous nature of JMS.
Hope this helps,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| Tchule |
| Posted: Mon May 27, 2002 10:54 pm Post subject: |
|
|
Newbie
Joined: 27 May 2002
Posts: 2
|
Thanks a lot, I've just implemented this solution, it works fine.
Merci. 
Tchule. |
|
| 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
|
|
|
|
