Author |
Message
|
hhoang |
Posted: Wed Aug 11, 2004 10:55 am Post subject: WebSphere failed to reconnect to MQ |
|
|
Novice
Joined: 14 Nov 2002 Posts: 21
|
We are using Windows 2003, WebSphere Applicaton Server 5.1 (WAS) and MQ 5.3.
Once in a while MQ is down for whatever reasons, and they start MQ again. When MQ comes up everything looks fine. However,
the WAS-server doesn't reconnect to the MQ-queue.
Is there a way to make WAS aware of the MQ when it comes up? Or is the only solution to restart WAS as well?
Thanks,
Hai hOANG |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Aug 11, 2004 11:07 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Whenever you need a maintenance interval for MQ you need to stop WAS.
The reason for it is that the MDB keep a constant connection to MQ.
If this connection is broken you're in trouble. (Unresponsive MDB's etc...)
On Unix the qmgr refuses to restart until all processes holding a connection to it have been killed...
Enjoy |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed Aug 11, 2004 1:34 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
See the last post in this thread on QMs coming down and MDBs. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
hhoang |
Posted: Mon Aug 16, 2004 6:49 am Post subject: Can you please give me the link |
|
|
Novice
Joined: 14 Nov 2002 Posts: 21
|
I can not find the link or the post your have suggested. Can you point me to it? Thanks, Hai |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Aug 16, 2004 11:51 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Aug 17, 2004 4:50 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Alternatively you can put an exception listener on each queue linked to an MDB and have the bean react to the onException event by releasing its resources and trying to acquire new ones....
Wait here goes another connection to the Qmgr....
Usually people just shutdown was before shutting down MQ....
Anyway shutting down MQ should be a planned maintenance...
Enjoy |
|
Back to top |
|
 |
|