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 IndexGeneral IBM MQ SupportSVRCONN channel behavior

Post new topicReply to topic
SVRCONN channel behavior View previous topic :: View next topic
Author Message
krypton
PostPosted: Fri Aug 18, 2017 8:45 am Post subject: SVRCONN channel behavior Reply with quote

Centurion

Joined: 14 Mar 2010
Posts: 112

Hi All,

I have a question regarding the behavior of "SVRCONN" channel, as per the below list the CHSTATI(Channel start time is diferent) but there is no value in any of the following parameters - MCAUSER, LSTMSGDA and LSTMSGTI
it means that no message transactions has taken place in any of the SVRCONN channel, so I am wondering why these Channel instances are running since 3 AM (17th Aug EST) , currently the time is 12:43 PM (18th Aug EST) means it is already more than 33 hours.

I am curious why more than 30 hours passed and channel doesn't seems to have even a single transactions taken place (based on LSTMSGTI) and why there are 11 instances of such channel(in all the channel the CONNNAME is same, all the parameters are same except JOBNAME).

Quote:
dis chs(ABC.CHLPRD) all
2 : dis chs(ABC.CHLPRD) all
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(03.47.10)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C3B9) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(04.10.15)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C4BB) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(04.17.16)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C4F4) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(04.24.17)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C528) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(04.31.19)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C55D) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(04.54.12)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C611) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(05.31.47)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C741) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(06.56.04)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000C9F9) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(07.03.06)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000CA65) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(07.57.34)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000CCB6) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)
AMQ8417: Display Channel Status details.
CHANNEL(ABC.CHLPRD) CHLTYPE(SVRCONN)
BUFSRCVD(5) BUFSSENT(4)
BYTSRCVD(1192) BYTSSENT(1080)
CHSTADA(2017-08-17) CHSTATI(08.04.35)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(19.129.139.99) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(000037C10000CCFF) LOCLADDR(::ffff:18.128.135.49(1415))
LSTMSGDA( ) LSTMSGTI( )
MCASTAT(RUNNING) MCAUSER( )
MONCHL(OFF) MSGS(0)
RAPPLTAG( ) SECPROT(TLSV1)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(SCYEXIT)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(08000002) RPRODUCT(MQJM)

_________________
Dreams are not something which you watch when you are asleep,it is something which doesn't let you sleep.
Back to top
View user's profile Send private message
hughson
PostPosted: Sat Aug 19, 2017 8:31 pm Post subject: Re: SVRCONN channel behavior Reply with quote

Shaman

Joined: 09 May 2013
Posts: 728
Location: Bay of Plenty, New Zealand

It would seem that every single one of your channel instances is currently in the Security Exit. You can tell this from the SUBSTATE attribute shown in your channel status output.

Code:
AMQ8417: Display Channel Status details.
   CHANNEL(ABC.CHLPRD)                   CHLTYPE(SVRCONN)
   BUFSRCVD(5)                             BUFSSENT(4)
   BYTSRCVD(1192)                          BYTSSENT(1080)
   CHSTADA(2017-08-17)                     CHSTATI(03.47.10)
   COMPHDR(NONE,NONE)                      COMPMSG(NONE,NONE)
   COMPRATE(0,0)                           COMPTIME(0,0)
   CONNAME(19.129.139.99)                  CURRENT
   EXITTIME(0,0)                           HBINT(300)
   JOBNAME(000037C10000C3B9)               LOCLADDR(::ffff:18.128.135.49(1415))
   LSTMSGDA( )                             LSTMSGTI( )
   MCASTAT(RUNNING)                        MCAUSER( )
   MONCHL(OFF)                             MSGS(0)
   RAPPLTAG( )                             SECPROT(TLSV1)
   SSLCERTI( )                             SSLKEYDA( )
   SSLKEYTI( )                             SSLPEER( )
   SSLRKEYS(0)                             STATUS(RUNNING)
   STOPREQ(NO)                             SUBSTATE(SCYEXIT)
   CURSHCNV(1)                             MAXSHCNV(10)
   RVERSION(08000002)                      RPRODUCT(MQJM)


krypton wrote:
there is no value in any of the following parameters - MCAUSER, LSTMSGDA and LSTMSGTI

This would also explain why no MCAUSER has been assigned to the channel yet because that happens once the security exit processing is complete (as it can be assigned by the security exit). Additionally no messages (or API calls) are allowed to flow across the channel until security exit processing has finished, so that explains why LSTMSGDA/TI are empty.

I suggest you review your security exit that is defined on this SVRCONN channel for code paths that might not return.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
krypton
PostPosted: Mon Aug 21, 2017 6:07 am Post subject: Reply with quote

Centurion

Joined: 14 Mar 2010
Posts: 112

Hi Morag, Thank you for reply.
Is there a possibility that it is the issue with Application itself instead of issue with Security exit?
May be application is creating un-necessary Channel connection without actually using them?
_________________
Dreams are not something which you watch when you are asleep,it is something which doesn't let you sleep.
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Aug 21, 2017 6:15 am Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 5749

krypton wrote:
Is there a possibility that it is the issue with Application itself instead of issue with Security exit?

Yes, in that it may spawn additional channel instances because it thinks the connection is hanging, but also if none of the channels are going beyond the exit sub-state there's probably an issue with the exit.

krypton wrote:
May be application is creating un-necessary Channel connection without actually using them?

See above.
_________________
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
View user's profile Send private message
hughson
PostPosted: Mon Aug 21, 2017 2:41 pm Post subject: Reply with quote

Shaman

Joined: 09 May 2013
Posts: 728
Location: Bay of Plenty, New Zealand

krypton wrote:
Is there a possibility that it is the issue with Application itself instead of issue with Security exit?
May be application is creating un-necessary Channel connection without actually using them?
If I were an application that tried to make a connection to the queue manager and after several hours it had not responded, I would not consider myself to be at fault if I made another connection.

While there is always a possibility that there is *ALSO* an issue with the application, you will not be able to tell until you fix the issue you can see is definitely there, that is the issue with the Security exit.

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
RogerLacroix
PostPosted: Tue Aug 22, 2017 9:36 am Post subject: Reply with quote

Jedi Knight

Joined: 15 May 2001
Posts: 3020
Location: London, ON Canada

What channel security exit are you using?

Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportSVRCONN channel behavior
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.