ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » svrconn channels not going away.

Post new topic  Reply to topic
 svrconn channels not going away. « View previous topic :: View next topic » 
Author Message
jrjoe
PostPosted: Thu Mar 16, 2006 12:48 pm    Post subject: svrconn channels not going away. Reply with quote

Acolyte

Joined: 20 Jan 2003
Posts: 60

I have Qmgr running on AIX 5.2 server and MQ version 5.3 CSD12.
I have the following set in the qm.ini for channels:

CHANNELS:
MaxChannels=300
MaxActiveChannels=200
AdoptNewMCA=ALL
AdoptNewMCATimeout=60
AdoptNewMCACheck=ALL

2 other things I was looking at that I saw in other postings.
are.

ClientIdle=300
TCP:
KeepAlive=Yes


The problem is I have MDB's connecting to the Qmgr with SVRCONNs from a WAS 5 server and I am expecting 4 connections but the number of connections continue to grow.

Should I use ClientIdle or will that close the connection regardless after the set time?
Also what will KeepAlive do if any to help with this?

Thanks in advance.
Joe
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Thu Mar 16, 2006 4:41 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

ClientIdle will kill any SVRCONN channels with no activity, so if the app connects and happens to be doing something other than MQ calls for Idle time, then they get the rug pulled out from beneath them, and a legit channel is killed.

MDBs usually are doing Get with Waits, and that wait interval is small, so they are always reissuing the MQGETs, so the channel should be seeing constant activity if the MDBs are still really connected. In this case ClientIdle will only kill bogus channels. Or channels that haven't done anything for a while.

TCP Keep Alive will only kill orphaned channels. Setting Keep Alive to yes means the QM will use the systems KeppAlive value, usually 2 hours. Probably want to lower that.

More than likely, the MDBs are "legit", (i.e. there are real MDBs on the other end, maybe not really needed, but there anyway) KeepAlive or ClientIdle won't come into play, and the app is just spawning more and more of them.

We use Capitalware's MQAUSX exit to put a limit on each SVRCONN channel, so no matter how bad they get, I have control as to how many they can start. We also use Keep Alive set to 15 minutes to squash orphaned connections. We DO NOT use ClientIdle since it can potentially kill legit channels.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
jrjoe
PostPosted: Thu Mar 16, 2006 6:26 pm    Post subject: Reply with quote

Acolyte

Joined: 20 Jan 2003
Posts: 60

Okay TCP Keep Alive will only kill orphaned channels but I didn't see them going away after a 2 hour period. If the MDB's are doing a Get with wait why does it continue to spawn new svrconn channels?

As far as the clientidle will that only kill svrconn channels?

It sounds like what I need to do is to set the systems KeepAlive to 15 minutes and KeepAlive to Yes and that should clean up the orphaned connections.

Thanks
Joe
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Mar 16, 2006 7:16 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

I'd suggest as well you read (search IBM site) "JMS Topologies". It is a very handy pdf that explains how many connections are needed with JMS And WAS. Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
PeterPotkay
PostPosted: Fri Mar 17, 2006 4:41 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

jrjoe wrote:
Okay TCP Keep Alive will only kill orphaned channels but I didn't see them going away after a 2 hour period. If the MDB's are doing a Get with wait why does it continue to spawn new svrconn channels?

First, verify with the sys admin that the server's Keep Alive is turned on, and if yes, that it's 2 hours, and not 2 years. Assuming it is on and set to 2 hours and the QM is set to use it AND the QM has been restarted after you turned its Keep Alive on, them most likely these are not orphaned connections. There still is a real tcp socket connection on the other end, so the QM will not drop them. Whether there is a happy and healthy MDB on that socket, who knows?

jrjoe wrote:

As far as the clientidle will that only kill svrconn channels?

Based on the verbiage in the below link, I would say only client channels (SVRCONNS):
http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSWHKB&q1=Clientidle&uid=swg21194427&loc=en_US&cs=utf-8&lang=en
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » svrconn channels not going away.
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.