Author |
Message
|
Studv01 |
Posted: Tue Sep 22, 2015 8:34 am Post subject: Max Channel Limit of a Queue Manager |
|
|
Apprentice
Joined: 23 Jan 2015 Posts: 27
|
Team
I see there is a value of Max Channel Limit in qm.ini to limit number of channel connections a QMGR can allow at any time. I was wondering if we can restrict number of connection each channel can have???
I am running on MQ Server V 7.5 and I have a condition that out of many applications that connect to a QMGR all of (or most of) client connection were consumed by one of the client application only that runs on Java 1.7.
I know there is a limitation at application side that restricts number of JMS connections but I am looking for any settings at MQ side to restrict number of client connections allowed through the Channel. |
|
Back to top |
|
 |
exerk |
Posted: Tue Sep 22, 2015 9:32 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Look at the MAXINST and MAXINSTC attributes of the SVRCONN object  _________________ 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 |
|
 |
Studv01 |
Posted: Wed Sep 23, 2015 1:08 pm Post subject: |
|
|
Apprentice
Joined: 23 Jan 2015 Posts: 27
|
thank you for the quick reply. the info helped
Have another question on the same note; how do I find out the optimum vale for MAXINST / MAXINSTC; I mean can I find out how many connections were established on a channel.
I know if I do a netstat on the listener port, I will get "ESTABLISHED" connections from a specific host; but is there a way I could find out how many active connections on a specific channel of a QMGR, in any other way? cause when I trouble I can not rely on netstat. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Sep 23, 2015 7:55 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Studv01 wrote: |
thank you for the quick reply. the info helped
Have another question on the same note; how do I find out the optimum vale for MAXINST / MAXINSTC; I mean can I find out how many connections were established on a channel.
I know if I do a netstat on the listener port, I will get "ESTABLISHED" connections from a specific host; but is there a way I could find out how many active connections on a specific channel of a QMGR, in any other way? cause when I trouble I can not rely on netstat. |
Try a display channel status and count the instances...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
tczielke |
Posted: Thu Sep 24, 2015 4:44 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010 Posts: 941 Location: Illinois, USA
|
When you run the DIS CHSTATUS, a command like the following would also be helpful:
dis chstatus(SRVR1.TO.SRVR2) jobname curshcnv
If you see output like the following:
CHANNEL(SRVR1.TO.SRVR2) CHLTYPE(SVRCONN)
CONNAME(10.20.30.40) CURRENT
JOBNAME(00000FCB000002FD) STATUS(RUNNING)
SUBSTATE(RECEIVE) CURSHCNV(10)
the CURSHCNV of 10 means there are 10 connections for this one channel instance.
If you want to know the pid and tid for this channel instance, it embedded in hex in the JOBNAME:
x'00000FCB' = 4043 is the pid
x'000002FD' = 765 is the tid _________________ Working with MQ since 2010. |
|
Back to top |
|
 |
Studv01 |
Posted: Thu Sep 24, 2015 8:18 am Post subject: |
|
|
Apprentice
Joined: 23 Jan 2015 Posts: 27
|
thank you both
here in my output, i have JOBNAME(00006095000F2015) and CURSHCNV(1); that means the PID in the "JOBNAME" - 00006095000F2015 is all one single PID in HEX?
and also i also have JOBNAME(0000589E0008D7C6) and CURSHCNV(2) that means i have 2 PIDs in "JOBNAME" - 0000589E (PID1) & 0008D7C6 (PID2) in HEX? |
|
Back to top |
|
 |
tczielke |
Posted: Thu Sep 24, 2015 8:31 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010 Posts: 941 Location: Illinois, USA
|
I can't say for sure if the JOBNAME always has this format, but for the examples you and I listed, the first 8 characters are the PID in hex, and the last 8 characters are the TID in hex.
For example,
JOBNAME(00006095000F2015)
would be
x'00006095' = 24,275 (pid)
x'000F2015' = 991,253 (tid)
and the CURSHCNV(1) means one connection is being managed under this channel pid/tid. More than likely the 24275 pid ties to an amqrmppa process. The tid 991,253 is just some internal number that MQ uses to track unique threads (tids).
For your other example, there were 2 connections "CURSHCNV(2)" for that channel pid/tid. _________________ Working with MQ since 2010. |
|
Back to top |
|
 |
Studv01 |
Posted: Thu Sep 24, 2015 10:49 am Post subject: |
|
|
Apprentice
Joined: 23 Jan 2015 Posts: 27
|
thank you "tczielke"; and alson thanks everyone for making things clear to me. |
|
Back to top |
|
 |
vennela |
Posted: Sun Sep 27, 2015 6:03 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Will the PID of any channel give anything other than one of the MQ processes? I am under the impression that it will never give us application PID. Atleast in the distributed world |
|
Back to top |
|
 |
Studv01 |
Posted: Wed Sep 30, 2015 12:35 pm Post subject: |
|
|
Apprentice
Joined: 23 Jan 2015 Posts: 27
|
then that means, there is no way we can figure out which clients connect to a specific channel in MQ? |
|
Back to top |
|
 |
tczielke |
Posted: Thu Oct 01, 2015 4:21 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010 Posts: 941 Location: Illinois, USA
|
If you can identify your client application by the channel name or queue being referenced, the following commands can help you track down the pid.tid of the SVRCONN channel that ties to your client application.
DIS CHSTATUS ALL
DIS CONN TYPE(ALL)
The client application can also help identify itself by setting the APPLTAG that appears in the DIS CONN.
If you can identify the pid.tid of the SVRCONN channel end for your client application, there is a cryptic way documented in this thread where you may be able to find the remote port that your client application is using -> http://www.mqseries.net/phpBB2/viewtopic.php?p=386727&sid=e6ebe5da3da4861520c46b62c0825ab6 _________________ Working with MQ since 2010. |
|
Back to top |
|
 |
|