|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
SVRCONN channel status increasing |
« View previous topic :: View next topic » |
Author |
Message
|
Muthukrishnan |
Posted: Thu Jun 23, 2016 4:55 am Post subject: SVRCONN channel status increasing |
|
|
Apprentice
Joined: 16 Feb 2013 Posts: 48
|
Hi ,
For some reason, we have got more SVRCONN connections than usual. Datapower (XB62) is connecting to MQ and using this SVRCONN. I see few connections from June 13, 2016 that are still active and running, and few in binding state as well. Can you please help me to resolve this? We are using MQ 7.5.0.2
Please refer few channel status as below
CHANNEL(XXX) CHLTYPE(SVRCONN)
BUFSRCVD(1) BUFSSENT(1)
BYTSRCVD(236) BYTSSENT(236)
CHSTADA(2016-06-17) CHSTATI(03.04.31)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(XX.XX.XXX.XXX) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(00005442000004F8) LOCLADDR( )
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( )
SSLCERTI(XX)
SSLKEYDA( ) SSLKEYTI( )
SSLPEER(XXX)
SSLRKEYS(0) STATUS(BINDING)
STOPREQ(NO) SUBSTATE(RECEIVE)
CURSHCNV(0) MAXSHCNV(0)
RVERSION(07000101) RPRODUCT(MQDP)
CHANNEL(XXX) CHLTYPE(SVRCONN)
BUFSRCVD(6934) BUFSSENT(6933)
BYTSRCVD(3077728) BYTSSENT(3077568)
CHSTADA(2016-06-13) CHSTATI(22.20.37)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(XX.XXX.XX.XX) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(00001EF300017B60) LOCLADDR( )
LSTMSGDA(2016-06-16) LSTMSGTI(08.05.12)
MCASTAT(RUNNING) MCAUSER(XXX)
MONCHL(OFF) MSGS(6931)
RAPPLTAG(WebSphere Datapower MQClient)
SSLCERTI(XXX)
SSLKEYDA( ) SSLKEYTI( )
SSLPEER(XX)
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(RECEIVE)
CURSHCNV(0) MAXSHCNV(0)
RVERSION(07000101) RPRODUCT(MQDP)
Note: KAINT is set as 'AUTO' in queue manager , cache timeout in datapower is set as '60 sec'. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jun 23, 2016 4:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Datapower will make one connection to MQ for each one it needs, per the configuration it has.
Each connection shows up as an instance of a running SVRCONN.
If you only want DP to ever make one connection to MQ, configure it to do so.
In other words, what you are seeing is a direct result of the Datapower configuration, and nothing wrong with MQ. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Muthukrishnan |
Posted: Thu Jun 23, 2016 5:03 am Post subject: |
|
|
Apprentice
Joined: 16 Feb 2013 Posts: 48
|
Thanks for your reply.
But my question is, why is the channel active from June 13 and why are few channels in binding state for long time? How do we resolve them? |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jun 23, 2016 5:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Check the MQ Error logs.
Check the Datapower logs. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Muthukrishnan |
Posted: Thu Jun 23, 2016 5:23 am Post subject: |
|
|
Apprentice
Joined: 16 Feb 2013 Posts: 48
|
Yeah. I did some analysis. I saw few lines as below. So if this is related to network glitches, then what are the best practices to be followed to resolve the errors? Please suggest.
Code: |
06/19/2016 05:01:53 AM - Process(14975.344) User(mqm) Program(amqrmppa)
Host(xxxx) Installation(Installation1)
VRMF(7.5.0.0) QMgr(xxx)
AMQ9208: Error on receive from host xxx (xxx).
EXPLANATION:
An error occurred receiving data from xxx (xxx) over TCP/IP.
This may be due to a communications failure.
ACTION:
The return code from the TCP/IP read() call was 104 (X'68'). Record these
values and tell the systems administrator.
|
|
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jun 23, 2016 5:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
First lock your network admins in a room with one laptop.
Second, repeat "It's a network problem" to them over and over and over again, until they actually start looking at things.
Once they've fixed the problem, or clearly demonstrated that it's not a network problem, feed them donuts and coffee.
There are no best practices for resolving particular types of errors. Other than "Perform normal debugging procedures". _________________ chmod -R ugo-wx / |
|
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
|
|
|
|