| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ client connecting to iSeries QM |
« View previous topic :: View next topic » |
| Author |
Message
|
| velocity |
 Posted: Wed Oct 28, 2009 10:38 am Post subject: MQ client connecting to iSeries QM |
 |
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
Hi Guys..We are having an issue where a dot net app using MQ client connects to an iSeries QM via SVRCONN. I see a lot of tcp ip get wait connections which if increases can bring down the system.
Have told the app to close the queue and disconnect from the queue but still see those.
Here is how the connections look like. I see 24 of these.
171.177.147.36 2593 1414 000:00:39 Time-wait
171.177.147.36 2596 1414 000:00:39 Time-wait
171.177.147.36 2601 1414 000:00:37 Time-wait
171.177.147.36 2602 1414 000:00:36 Time-wait
171.177.147.36 2609 1414 000:00:25 Time-wait
171.177.147.36 2611 1414 000:00:24 Time-wait
171.177.147.36 2612 1414 000:00:24 Time-wait |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Oct 28, 2009 2:17 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Closing the queue, and the disconnecting from the queue manager (note: not queue) is not a very efficient thing to suggest...better to limit the maximum number of connections - there is no way that clients connecting should bring down a system. If the connections you are seeing are 'stale' handles, then fix the cause, i.e. make sure the client does close and disconnect properly when it needs to.
_________________
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 |
|
|
| colbype |
| Posted: Fri Oct 30, 2009 5:59 pm Post subject: Iseries |
|
|
Novice
Joined: 13 Jan 2009
Posts: 23
|
Check the channel and see how many connections he has on the server conn channel he is using.
Seems like he is opening up new channel connection without disconnection the one he is already on. You can use the Blockip2 exit on the iseries to limit the number of connections an app can have on a channel. You can compile the C code on the iseries and then put the .ini file in the IFS directory.
If you are on V7 of MQ you can restrict the channel connections from the qm.ini file. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Oct 30, 2009 6:27 pm Post subject: Re: Iseries |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| colbype wrote: |
| If you are on V7 of MQ you can restrict the channel connections from the qm.ini file. |
You can restrict the total number of active channels in the qm.ini file of any (recent) MQ version, not just version 7.
As of MQ 7, you can restrict the # of instances of any particular channel by altering the channel definition itself, not the qm.ini file.
Neither of these 2 things will clean up the old and possibly orphaned connections, although they will keep that one app from sucking up all your available channels and thus impacting other channels' ability to start.
TCP Keep Alive, ClientIdle and better application coding can all be helpful in preventing too many connnections and / or cleaning up orphaned connections.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| colbype |
| Posted: Fri Oct 30, 2009 9:37 pm Post subject: |
|
|
Novice
Joined: 13 Jan 2009
Posts: 23
|
|
| 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
|
|
|
|
