Re: To many SVRCONN Connections on WebSphere MQ V5.3
There are two things that can be done: One is to check if the current version of MQ that you are using properly close the connection. MQ5.2 up to csd04 had problem, i.e. if the program was not disconnected gracefully, it will think that the connection to the queue manager is still open. I would check with IBM to see if that problem was carried over to MQ5.3 or not. Two is to insure that the program closes the connection, but you have no control ... --- Nick Dilauro <[EMAIL PROTECTED]> wrote: > You should also check the server side setting since > the default is sometimes > high (On Windows the default is something like 2 > hours). I'm not that > familiar with AIX but the following might help. > www.sybase.com/detail?id=611 > <http://www.sybase.com/detail?id=611> > > Nick > > > -Original Message- > From: Bill Anderson [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 23, 2003 12:10 PM > To: [EMAIL PROTECTED] > Subject: Re: To many SVRCONN Connections on > WebSphere MQ V5.3 > > I did forget to mention this is on AIX 3.3 / > WebSphere MQ V5.3. > > And that is half of my problem, I don't know if the > clients are holding on > to the connection or not. I guess it is worth > setting up the KeepAlive > settings in the mq.ini file (I think that's where it > goes) and see if it > helps at all. > > Does anyone know if the problem with the Java client > is correct as I > explained it in my original post? I got the info > from a lecture I attended > in Vegas early this year. As I said, all of these > connections are from > external customers, so I can't do much about their > code. But it would be > nice to be able to give them some solid clues on > what to do. > > Bill Anderson > Senior Systems Analyst > SITA Atlanta, GA > 770-303-3503 (office) > 404-915-3190 (cell) > [EMAIL PROTECTED] > http://www.mconnect.aero/ > > > > Nick Dilauro > <[EMAIL PROTECTED] To: > [EMAIL PROTECTED] > >cc: > Sent by: MQSeries > Subject: Re: To many SVRCONN > Connections on WebSphere MQ V5.3 > List > <[EMAIL PROTECTED] > N.AC.AT> > > > 10/23/2003 02:02 > PM > Please respond to > MQSeries List > > > > > > > This problem might be solved by a TCP/IP KeepAlive > setting. It needs to be > set on the server and in the qmgr. What platform > are you on? If the > clients are actually holding on to all the > connections this won't work. > > Nick > > -Original Message- > From: Bill Anderson [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 23, 2003 10:25 AM > To: [EMAIL PROTECTED] > Subject: To many SVRCONN Connections on WebSphere MQ > V5.3 > > On several occasions, we have had customers making > 30 + (one did over 200) > connections to a server connection channel. Each > customer has a dedicated > channel used only by them. Almost all of the > connections have very low > message counts (like 4 or 6) that do not change. > Only one or two have > significant message counts (like 500 + and rising). > > I am assuming that their applications are > misbehaving by making erroneous > connections for some reason. Many of the customers > had contractors develop > the code, and they have no Idea what it is doing > (great !) but they agree > they do not intend to make so many connections. I > remember hearing that > applications written as Java clients can experience > false 2009 errors > which, could cause them to re-connect. The problem > being that the original > connections is still valid. That would explain the > problem I think. > > But regardless of the cause of the problem, I need a > way to manage it on my > side. I can't limit the number of connections on a > channel by channel basis > so I need to figure out a way to discover erroneous > connections and kill > them. They all come from the same IP address, and > that don't help at all. I > may have to just bring the whole channel down and > restart it. > > But I would really like to find a way to have the > queue manager end the > channels that are not in use. If the connection > between a client > application and an in between router was truly lost, > but the queue manager > side of the router was OK, would the queue manager > not at some point clean > up the defunct connection? > > > > Bill Anderson > Senior Systems Analyst > SIT
Re: To many SVRCONN Connections on WebSphere MQ V5.3
Title: RE: To many SVRCONN Connections on WebSphere MQ V5.3 You should also check the server side setting since the default is sometimes high (On Windows the default is something like 2 hours). I'm not that familiar with AIX but the following might help. www.sybase.com/detail?id=611 Nick -Original Message- From: Bill Anderson [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 23, 2003 12:10 PM To: [EMAIL PROTECTED] Subject: Re: To many SVRCONN Connections on WebSphere MQ V5.3 I did forget to mention this is on AIX 3.3 / WebSphere MQ V5.3. And that is half of my problem, I don't know if the clients are holding on to the connection or not. I guess it is worth setting up the KeepAlive settings in the mq.ini file (I think that's where it goes) and see if it helps at all. Does anyone know if the problem with the Java client is correct as I explained it in my original post? I got the info from a lecture I attended in Vegas early this year. As I said, all of these connections are from external customers, so I can't do much about their code. But it would be nice to be able to give them some solid clues on what to do. Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Nick Dilauro <[EMAIL PROTECTED] To: [EMAIL PROTECTED] > cc: Sent by: MQSeries Subject: Re: To many SVRCONN Connections on WebSphere MQ V5.3 List <[EMAIL PROTECTED] N.AC.AT> 10/23/2003 02:02 PM Please respond to MQSeries List This problem might be solved by a TCP/IP KeepAlive setting. It needs to be set on the server and in the qmgr. What platform are you on? If the clients are actually holding on to all the connections this won't work. Nick -Original Message- From: Bill Anderson [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 23, 2003 10:25 AM To: [EMAIL PROTECTED] Subject: To many SVRCONN Connections on WebSphere MQ V5.3 On several occasions, we have had customers making 30 + (one did over 200) connections to a server connection channel. Each customer has a dedicated channel used only by them. Almost all of the connections have very low message counts (like 4 or 6) that do not change. Only one or two have significant message counts (like 500 + and rising). I am assuming that their applications are misbehaving by making erroneous connections for some reason. Many of the customers had contractors develop the code, and they have no Idea what it is doing (great !) but they agree they do not intend to make so many connections. I remember hearing that applications written as Java clients can experience false 2009 errors which, could cause them to re-connect. The problem being that the original connections is still valid. That would explain the problem I think. But regardless of the cause of the problem, I need a way to manage it on my side. I can't limit the number of connections on a channel by channel basis so I need to figure out a way to discover erroneous connections and kill them. They all come from the same IP address, and that don't help at all. I may have to just bring the whole channel down and restart it. But I would really like to find a way to have the queue manager end the channels that are not in use. If the connection between a client application and an in between router was truly lost, but the queue manager side of the router was OK, would the queue manager not at some point clean up the defunct connection? Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: To many SVRCONN Connections on WebSphere MQ V5.3
All... Try lowering the heartbeat interval from the 300 default to 30 seconds then change the queue manager configuration by adding the AdoptNewMCA=ALL & AdoptNewMCACheck=ALL. Check the System Admin guide for details... Phil Scott Gray <[EMAIL PROTECTED]To: [EMAIL PROTECTED] >cc: Sent by: MQSeriesSubject: Re: To many SVRCONN Connections on WebSphere MQ V5.3 List <[EMAIL PROTECTED] n.AC.AT> 10/23/2003 02:10 PM Please respond to MQSeries List actually you can...there is a MAXCONN channel exit. Look at: http://www-3.ibm.com/software/integration/support/supportpacs/individual/me7 1.html Source is provided. Scott -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Bill Anderson Sent: Thursday, October 23, 2003 1:25 PM To: [EMAIL PROTECTED] Subject: To many SVRCONN Connections on WebSphere MQ V5.3 On several occasions, we have had customers making 30 + (one did over 200) connections to a server connection channel. Each customer has a dedicated channel used only by them. Almost all of the connections have very low message counts (like 4 or 6) that do not change. Only one or two have significant message counts (like 500 + and rising). I am assuming that their applications are misbehaving by making erroneous connections for some reason. Many of the customers had contractors develop the code, and they have no Idea what it is doing (great !) but they agree they do not intend to make so many connections. I remember hearing that applications written as Java clients can experience false 2009 errors which, could cause them to re-connect. The problem being that the original connections is still valid. That would explain the problem I think. But regardless of the cause of the problem, I need a way to manage it on my side. I can't limit the number of connections on a channel by channel basis so I need to figure out a way to discover erroneous connections and kill them. They all come from the same IP address, and that don't help at all. I may have to just bring the whole channel down and restart it. But I would really like to find a way to have the queue manager end the channels that are not in use. If the connection between a client application and an in between router was truly lost, but the queue manager side of the router was OK, would the queue manager not at some point clean up the defunct connection? Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: To many SVRCONN Connections on WebSphere MQ V5.3
I did forget to mention this is on AIX 3.3 / WebSphere MQ V5.3. And that is half of my problem, I don't know if the clients are holding on to the connection or not. I guess it is worth setting up the KeepAlive settings in the mq.ini file (I think that's where it goes) and see if it helps at all. Does anyone know if the problem with the Java client is correct as I explained it in my original post? I got the info from a lecture I attended in Vegas early this year. As I said, all of these connections are from external customers, so I can't do much about their code. But it would be nice to be able to give them some solid clues on what to do. Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Nick Dilauro <[EMAIL PROTECTED]To: [EMAIL PROTECTED] >cc: Sent by: MQSeries Subject: Re: To many SVRCONN Connections on WebSphere MQ V5.3 List <[EMAIL PROTECTED] N.AC.AT> 10/23/2003 02:02 PM Please respond to MQSeries List This problem might be solved by a TCP/IP KeepAlive setting. It needs to be set on the server and in the qmgr. What platform are you on? If the clients are actually holding on to all the connections this won't work. Nick -Original Message- From: Bill Anderson [mailto:[EMAIL PROTECTED] Sent: Thursday, October 23, 2003 10:25 AM To: [EMAIL PROTECTED] Subject: To many SVRCONN Connections on WebSphere MQ V5.3 On several occasions, we have had customers making 30 + (one did over 200) connections to a server connection channel. Each customer has a dedicated channel used only by them. Almost all of the connections have very low message counts (like 4 or 6) that do not change. Only one or two have significant message counts (like 500 + and rising). I am assuming that their applications are misbehaving by making erroneous connections for some reason. Many of the customers had contractors develop the code, and they have no Idea what it is doing (great !) but they agree they do not intend to make so many connections. I remember hearing that applications written as Java clients can experience false 2009 errors which, could cause them to re-connect. The problem being that the original connections is still valid. That would explain the problem I think. But regardless of the cause of the problem, I need a way to manage it on my side. I can't limit the number of connections on a channel by channel basis so I need to figure out a way to discover erroneous connections and kill them. They all come from the same IP address, and that don't help at all. I may have to just bring the whole channel down and restart it. But I would really like to find a way to have the queue manager end the channels that are not in use. If the connection between a client application and an in between router was truly lost, but the queue manager side of the router was OK, would the queue manager not at some point clean up the defunct connection? Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: To many SVRCONN Connections on WebSphere MQ V5.3
What platform and CSD are you on? we had a lot of defunct processes on 5.2 after applying the latest CSD at that time it has stopped. We migrated from 5.2 CSD 5 to 5.3 CSD4 (where we don't see this behaviour either), so it could be solved by a CSD. Michael -Oorspronkelijk bericht- Van: MQSeries List [mailto:[EMAIL PROTECTED] Bill Anderson Verzonden: donderdag 23 oktober 2003 19:25 Aan: [EMAIL PROTECTED] Onderwerp: To many SVRCONN Connections on WebSphere MQ V5.3 On several occasions, we have had customers making 30 + (one did over 200) connections to a server connection channel. Each customer has a dedicated channel used only by them. Almost all of the connections have very low message counts (like 4 or 6) that do not change. Only one or two have significant message counts (like 500 + and rising). I am assuming that their applications are misbehaving by making erroneous connections for some reason. Many of the customers had contractors develop the code, and they have no Idea what it is doing (great !) but they agree they do not intend to make so many connections. I remember hearing that applications written as Java clients can experience false 2009 errors which, could cause them to re-connect. The problem being that the original connections is still valid. That would explain the problem I think. But regardless of the cause of the problem, I need a way to manage it on my side. I can't limit the number of connections on a channel by channel basis so I need to figure out a way to discover erroneous connections and kill them. They all come from the same IP address, and that don't help at all. I may have to just bring the whole channel down and restart it. But I would really like to find a way to have the queue manager end the channels that are not in use. If the connection between a client application and an in between router was truly lost, but the queue manager side of the router was OK, would the queue manager not at some point clean up the defunct connection? Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: To many SVRCONN Connections on WebSphere MQ V5.3
actually you can...there is a MAXCONN channel exit. Look at: http://www-3.ibm.com/software/integration/support/supportpacs/individual/me7 1.html Source is provided. Scott -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Bill Anderson Sent: Thursday, October 23, 2003 1:25 PM To: [EMAIL PROTECTED] Subject: To many SVRCONN Connections on WebSphere MQ V5.3 On several occasions, we have had customers making 30 + (one did over 200) connections to a server connection channel. Each customer has a dedicated channel used only by them. Almost all of the connections have very low message counts (like 4 or 6) that do not change. Only one or two have significant message counts (like 500 + and rising). I am assuming that their applications are misbehaving by making erroneous connections for some reason. Many of the customers had contractors develop the code, and they have no Idea what it is doing (great !) but they agree they do not intend to make so many connections. I remember hearing that applications written as Java clients can experience false 2009 errors which, could cause them to re-connect. The problem being that the original connections is still valid. That would explain the problem I think. But regardless of the cause of the problem, I need a way to manage it on my side. I can't limit the number of connections on a channel by channel basis so I need to figure out a way to discover erroneous connections and kill them. They all come from the same IP address, and that don't help at all. I may have to just bring the whole channel down and restart it. But I would really like to find a way to have the queue manager end the channels that are not in use. If the connection between a client application and an in between router was truly lost, but the queue manager side of the router was OK, would the queue manager not at some point clean up the defunct connection? Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: To many SVRCONN Connections on WebSphere MQ V5.3
This problem might be solved by a TCP/IP KeepAlive setting. It needs to be set on the server and in the qmgr. What platform are you on? If the clients are actually holding on to all the connections this won't work. Nick -Original Message- From: Bill Anderson [mailto:[EMAIL PROTECTED] Sent: Thursday, October 23, 2003 10:25 AM To: [EMAIL PROTECTED] Subject: To many SVRCONN Connections on WebSphere MQ V5.3 On several occasions, we have had customers making 30 + (one did over 200) connections to a server connection channel. Each customer has a dedicated channel used only by them. Almost all of the connections have very low message counts (like 4 or 6) that do not change. Only one or two have significant message counts (like 500 + and rising). I am assuming that their applications are misbehaving by making erroneous connections for some reason. Many of the customers had contractors develop the code, and they have no Idea what it is doing (great !) but they agree they do not intend to make so many connections. I remember hearing that applications written as Java clients can experience false 2009 errors which, could cause them to re-connect. The problem being that the original connections is still valid. That would explain the problem I think. But regardless of the cause of the problem, I need a way to manage it on my side. I can't limit the number of connections on a channel by channel basis so I need to figure out a way to discover erroneous connections and kill them. They all come from the same IP address, and that don't help at all. I may have to just bring the whole channel down and restart it. But I would really like to find a way to have the queue manager end the channels that are not in use. If the connection between a client application and an in between router was truly lost, but the queue manager side of the router was OK, would the queue manager not at some point clean up the defunct connection? Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
To many SVRCONN Connections on WebSphere MQ V5.3
On several occasions, we have had customers making 30 + (one did over 200) connections to a server connection channel. Each customer has a dedicated channel used only by them. Almost all of the connections have very low message counts (like 4 or 6) that do not change. Only one or two have significant message counts (like 500 + and rising). I am assuming that their applications are misbehaving by making erroneous connections for some reason. Many of the customers had contractors develop the code, and they have no Idea what it is doing (great !) but they agree they do not intend to make so many connections. I remember hearing that applications written as Java clients can experience false 2009 errors which, could cause them to re-connect. The problem being that the original connections is still valid. That would explain the problem I think. But regardless of the cause of the problem, I need a way to manage it on my side. I can't limit the number of connections on a channel by channel basis so I need to figure out a way to discover erroneous connections and kill them. They all come from the same IP address, and that don't help at all. I may have to just bring the whole channel down and restart it. But I would really like to find a way to have the queue manager end the channels that are not in use. If the connection between a client application and an in between router was truly lost, but the queue manager side of the router was OK, would the queue manager not at some point clean up the defunct connection? Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
