| Author |
Message
|
| wschutz |
 Posted: Wed Feb 22, 2006 4:14 am Post subject: |
 |
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| sido wrote: |
Hi mvic,
Thanks for the article...it did help. However, saw a line in the second link that raises some doubts!
>>>>> This attribute is supported on z/OS(R) only. |
Correct, MAXCHL(integer) as an mqsc command is only relevant to zOS, the equivalent is the keyword setting in the qm.ini file.
But I think you should first understand why you have so many channels running in the first place... start by seeing what you can from issuing a DISPLAY CHSTATUS(*) ALL command .
_________________
-wayne |
|
| Back to top |
|
 |
| mvic |
| Posted: Wed Feb 22, 2006 4:25 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
|
| Back to top |
|
|
| sido |
| Posted: Wed Feb 22, 2006 9:14 pm Post subject: |
|
|
Novice
Joined: 02 Feb 2004
Posts: 23
|
Hi,
Did the display chstatus(*) command and found only 20 channel instances running. Here is what I got:
DISPLAY CHSTATUS(*)
1 : DISPLAY CHSTATUS(*)
AMQ8417: Display Channel Status details.
CHANNEL(CUP.UNIFY_ISS.CH) XMITQ( )
CONNAME(145.17.50. CURRENT
CHLTYPE(RCVR) STATUS(RUNNING)
RQMNAME(ISSQM)
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
AMQ8417: Display Channel Status details.
CHANNEL(CHANNEL1) XMITQ( )
CONNAME(127.0.0.1) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
RQMNAME( )
something's missing here!
| wschutz wrote: |
| sido wrote: |
Hi mvic,
Thanks for the article...it did help. However, saw a line in the second link that raises some doubts!
>>>>> This attribute is supported on z/OS(R) only. |
Correct, MAXCHL(integer) as an mqsc command is only relevant to zOS, the equivalent is the keyword setting in the qm.ini file.
But I think you should first understand why you have so many channels running in the first place... start by seeing what you can from issuing a DISPLAY CHSTATUS(*) ALL command . |
|
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Feb 23, 2006 3:33 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Thats very interesting, just to double check, can you post your qm.ini here. And also the relevant section from the AMQERR01.LOG.
_________________
-wayne |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 23, 2006 3:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| Code: |
stop chl(channel1) mode(force) status(stopped)
* wait for some time
start chl(channel1) |
This should clear it up.
The question is really why do you have so many connections from the same box (127.0.0.1 loopback) ?
Do you have some program that is not disconnecting properly ?
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sido |
| Posted: Thu Feb 23, 2006 8:54 pm Post subject: |
|
|
Novice
Joined: 02 Feb 2004
Posts: 23
|
Hi,
Here is what is the current setting on the App Server QM qm.ini file -
#*******************************************************************#
#* Module Name: qm.ini *#
#* Type : WebSphere MQ queue manager configuration file *#
# Function : Define the configuration of a single queue manager *#
#* *#
#*******************************************************************#
#* Notes : *#
#* 1) This file defines the configuration of the queue manager *#
#* *#
#*******************************************************************#
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
#* *#
#* *#
Log:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogPath=/var/mqm/log/UFYQM/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/mqm/lib/amqzfu
ComponentDataSize=0
TCP:
KeepAlive=Yes
CHANNELS:
MaxChannels=500
HERE IS A SUBSECTION OF THE AMQERR03.LOG -
02/19/06 11:30:26
AMQ9209: Connection to host 'loopback (127.0.0.1)' closed.
EXPLANATION:
An error occurred receiving data from 'loopback (127.0.0.1)' over TCP/IP. The
connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- amqccita.c : 2736 -------------------------------------------------------
02/19/06 11:51:52
AMQ9513: Maximum number of channels reached.
EXPLANATION:
The maximum number of channels that can be in use simultaneously has been
reached. The number of permitted channels is a configurable parameter in the
queue manager configuration file.
ACTION:
Wait for some of the operating channels to close. Retry the operation when some
channels are available.
----- amqrcsia.c : 1028 -------------------------------------------------------
02/19/06 11:51:52
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CHANNEL1' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CHANNEL1' in the error
files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
02/19/06 11:53:26
AMQ9513: Maximum number of channels reached.
EXPLANATION:
The maximum number of channels that can be in use simultaneously has been
reached. The number of permitted channels is a configurable parameter in the
queue manager configuration file.
ACTION:
Wait for some of the operating channels to close. Retry the operation when some
channels are available.
----- amqrcsia.c : 1028 -------------------------------------------------------
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Feb 24, 2006 6:10 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
It doesn't matter what your settings are, or how often you stop the channel and restart it.
If you have an app that is not closing its connections, and it keeps opening more than you have available, you will get this problem.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| sirsi |
| Posted: Thu Apr 20, 2006 7:40 pm Post subject: |
|
|
Disciple
Joined: 11 Mar 2005
Posts: 177
|
as PeterPotkay said:
| Quote: |
| if you have an app that's looping, not closing its connections, then it doesn't matter if you set max channels to 500, 1000 or 10,000. |
the only constraint here is the hardware resource... |
|
| Back to top |
|
|
|
|
