| Author |
Message
|
| kun.leeing |
 Posted: Thu Mar 12, 2009 11:15 pm Post subject: port can not be started after a large number of connections |
 |
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
I take a test of connecting qmgr with many clients using one port.
I created 10 svrconn channels seperated and every channel holded 200 session. when I wanted to make more connections from clients it returned 'qmgr can not available' . Then I looked over my mq server, the qmgr had been stopped.After this, whatever I took, the port could not be started even though I restarted my qmgr. (my mq.ini MaxActiveChannels, MaxChannels, MaxInitiatorChannels all set 50000)
How can I solve this problem? and How many connections can one port sustain?
Thanks,experts. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Fri Mar 13, 2009 1:17 am Post subject: Re: port can not be started after a large number of connecti |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| kun.leeing wrote: |
How can I solve this problem? and How many connections can one port sustain?
|
you should ask, how many connections will OS allow. its not MQ who does this.
you have to set Maximum User Connections, and search for TCPKeepAlive attribute also in this forum, you will get proper answer.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Mar 13, 2009 1:17 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I'm not altogether sure precisely what you mean but have you checked that your Listener is actually running?
_________________
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 |
|
|
| kun.leeing |
| Posted: Fri Mar 13, 2009 4:58 pm Post subject: |
|
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
Thanks, for all your replies.
My TCPKeepAlive have set to YES and the port can not be started. It will be stopped after holding status of running for about three seconds even though I open it manually.
thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 14, 2009 2:08 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| kun.leeing wrote: |
Thanks, for all your replies.
My TCPKeepAlive have set to YES and the port can not be started. It will be stopped after holding status of running for about three seconds even though I open it manually.
thanks. |
That makes little sense.
You need to check if there is a process running on your port. (netstat -an)
You need to check the control for the listener defined in MQ. It should be qmgr. When closing the qmgr make sure the MQ listener gets shutdown as well. If need be force it to close (endmqlsr -f -m qmgr)
Assuming that you have no firewall problem...
Check the listener status when the qmgr comes back up. If it is not started start it manually. Verify value of control field.
Before the qmgr gets started verify that no processes are still running against that port (netstat -an). If there still are some investigate why. Make sure all channel processes have stopped.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kun.leeing |
| Posted: Sat Mar 14, 2009 7:11 am Post subject: |
|
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
Thanks,saper.
Yes, there was process on the port. I started the port by killing process.
But the key question is why the qmgr stopped after a large number of connections on the port. Of course the port has been driven to stop.
It seems like the port can not afford great many of clients connecting simultaneously. When exceeding the limit of connection number, the channel and port will be stopped firstly , and then my qmgr become 'RED' automatically.
This is what I just wonder why one port failed can impact its qmgr?
This is terrible. What about the other apps and channels on the other ports?
I don't know if I clear my meaning. oh, my poor english. 
But thanks for the quick response above. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 14, 2009 3:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you set your max connections by channel (V7), you should have a minimum impact.
Remember you're only limited by the max connections on port supported by your OS. Now if you allow a tcp queue there you may get some more but to the expense of speed.
The whole qmgr is impacted when you hit your maxchannels/maxactivechannels limit. That is when the qmgr becomes unresponsive until some connections are freed. You don't have to bounce it. Just access it with runmqsc and force close the offending channel. Fix what caused the multiple connections (probably a network problem) and restart the channel. Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kun.leeing |
| Posted: Tue Mar 17, 2009 6:27 pm Post subject: |
|
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
Thanks for your reply. 
I'll try it. |
|
| Back to top |
|
|
|
|
