Author |
Message
|
atheek |
Posted: Wed Aug 20, 2008 6:53 pm Post subject: Listener cannot bind to port after MSCS failover |
|
|
 Partisan
Joined: 01 Jun 2006 Posts: 327 Location: Sydney
|
MQ Version : 6.0.2.3
Windows 2003
We have setup MSCS with active/passive qmgr configuration across 2 nodes. There are different app server instances (weblogic, running on both nodes ) which connects to the queue manager.
During maintainance on the primary node, the queue manager is failed over to other node along with the app server instances that was running on the primary node. Everything is fine now. Passive QMGR kicks start and app servers are up and running.
After the completion of the maintainance activities on the primary node, the queue manager and app servers are moved back to the primary node. At this time, the queue manager listener process fails to start as it complains that it cannot bind to the port. If I do a netstat for the port , I can see stale connections that are in an established state with the destination socket as queue manager port.
I feel this might not be an issue with MQ and should be an OS ( TCP/IP) issue. But still like to know if any one here has come across this:
Also was thinking whether the order in which the groups are moved like app servers first followed by MQ etc have any part in this.
Appreciate your valuable comments
TIA,
Atheek |
|
Back to top |
|
 |
exerk |
Posted: Thu Aug 21, 2008 12:54 am Post subject: Re: Listener cannot bind to port after MSCS failover |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
atheek wrote: |
...Also was thinking whether the order in which the groups are moved like app servers first followed by MQ etc have any part in this... |
As a general rule groups should be taken down in order of dependency, i.e. if Group A has a dependency on Group B, then Group A should be off-lined first but on-lined second.
Is the Listener queue manager controlled, or MSCS controlled? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
atheek |
Posted: Thu Aug 21, 2008 2:48 am Post subject: |
|
|
 Partisan
Joined: 01 Jun 2006 Posts: 327 Location: Sydney
|
listener is queue manager controlled...only qmgr, disk,ip and network name comes under the cluster group... |
|
Back to top |
|
 |
exerk |
Posted: Thu Aug 21, 2008 3:26 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
OK. Last time I did MSCS and WMQ was with V5.3. I can't find anything explicit in the Info Centre about not putting the Listener under MSCS control (and before the ire of the Mod's descends upon me regarding Listeners in V6.0, I know the preference is for them to be under queue manager control) but has that been tried? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
atheek |
Posted: Thu Aug 21, 2008 3:54 am Post subject: |
|
|
 Partisan
Joined: 01 Jun 2006 Posts: 327 Location: Sydney
|
|
Back to top |
|
 |
PeterPotkay |
Posted: Thu Aug 21, 2008 10:27 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Do a search on this site for a post by me on this topic. I found that bug when we went to MQ 6.0.2.1. An orphaned Listener is being left behind. They gave me a hot fix for 6.0.2.1. I don't know if its fixed in 6.0.2.3, but it is fixed in 6.0.2.4 _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
atheek |
Posted: Fri Aug 22, 2008 1:09 am Post subject: |
|
|
 Partisan
Joined: 01 Jun 2006 Posts: 327 Location: Sydney
|
Hi Peter,
I spent a good 20 minutes seraching for your post here...but couldnt get it ' '
I would like to know what you mean by "orphaned listener" here. when listener complains that it cant bind to the port, I do a netstat, I could only see some connections from the app server to the listener port. I cant see anything running at that port with the status "Listening". Is this the same behaviour what you were getting. As a workaround, we need to bring down the app servers from which the stale connections originate and then restart the queue manager. This makes the listener to start. I am looking at where exactly the problem could be : there are 3 suspects MQ, app servers or the OS , so would like to pin down the real culprit
Thanks,
Atheek |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Aug 22, 2008 10:10 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Check that anybody using MDB's has also set "FAIL IF QUIESCE" on their QCF/TCF  _________________ MQ & Broker admin |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Aug 22, 2008 12:24 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
|
Back to top |
|
 |
atheek |
Posted: Sat Aug 23, 2008 4:40 pm Post subject: |
|
|
 Partisan
Joined: 01 Jun 2006 Posts: 327 Location: Sydney
|
From your post there it appears this is fixed in 6.0.2.3. We already have 6.0.2.3...........
FJ, all the qcf's used by the app servers has FAILIFQUIESCE(YES). I think this is the default setting. We haven't modified this...Can you let me know what implications this has..
Thanks,
Atheek |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Aug 24, 2008 3:25 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
atheek wrote: |
From your post there it appears this is fixed in 6.0.2.3. We already have 6.0.2.3...........
FJ, all the qcf's used by the app servers has FAILIFQUIESCE(YES). I think this is the default setting. We haven't modified this...Can you let me know what implications this has..
Thanks,
Atheek |
I have seen boxes where you cannot restart the qmgr without restarting WAS
The MDB's in WAS keep a process on the qmgr even though the qmgr has been shutdown. To restart the qmgr you have to recycle WAS MDB or recycle WAS.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Aug 25, 2008 3:31 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
|
Back to top |
|
 |
|