| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to trace MQ Listener? |
« View previous topic :: View next topic » |
| Author |
Message
|
| issac |
 Posted: Mon May 03, 2010 4:05 am Post subject: How to trace MQ Listener? |
 |
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
I have a problematic listener in the product env. Clients begin to fail to connect to QMGR about 4 days after runmqlsr is started. What's more, not all clients have the problem. Some connects to the QMGR well.
I've ensured that no word like MaxChannel or MaxActiveChannel is present in any log.
Actually I found nothing at all useful in logs, the previous log was created during QMGR startup.
Restarting runmqlsr process solves the issue every time. MQ version is 530 CSD06.
Now I wish to trace the runmqlsr, or at least gather some log about the listener. I have no idea what's going wrong fow now. The system has been online for 2 years, and the phenomenon only occurred for the first time 2 months ago. I've inquired about network env changes and hardware changes, nothing seems prone to be the cause.
_________________
Bazinga! |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon May 03, 2010 4:25 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
With no MaxChannel set then the queue manager will 'default' to the setting of 100 (IIRC the default) and MaxActiveChannel will match that limit. As regards the clients, what is in their logs? Have the number of clients increased? Are there 'orphan' connections? And why do you suspect the Listener?
_________________
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 |
|
|
| PeterPotkay |
| Posted: Mon May 03, 2010 4:32 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I think issac means there are no errors in his QM logs that mentione max channels being hit.
Is there a security exit configured on the channel that may be blocking connections occasionally for legitimate reasons?
The MQ Listener can only deal with a certain # of concurrent connection attempts at once. The default # varies by platform and is configurable. If you get a burst of clients all wanting to connect at the same time and you exceed that #, some will be rejected.
Having it work after restarting the runmqlsr process may just be a coincidence.
Or you may have a real problem that is solved by recycling the listener. I've never run into one like that yet. Have a look at all the fixes to MQ 5.3 since CSD6. CSD14 may contain a relelvent fix. Although you should be looking to upgrade to MQ 6 or MQ 7. The software you are running is years out of support.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
