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 Index » General IBM MQ Support » MQ client connection channel is not closing

Post new topic  Reply to topic Goto page Previous  1, 2
 MQ client connection channel is not closing « View previous topic :: View next topic » 
Author Message
bruce2359
PostPosted: Sat Nov 21, 2015 7:03 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9405
Location: US: west coast, almost. Otherwise, enroute.

depuk wrote:
Thanks for your replies Peter,Jeff and bruce.I gone through the link provided. I didn't understand this point.Please explain me

The SVRCONN inactivity interval applies only between WebSphere MQ API calls from a client, so no client is disconnected during an extended MQGET with wait call


and i am using amqsputc to test my changes.Application team is not ready to make changes at thier side.Please confirm me is it fine with my changes.

Confusing, as amqsputc does not use the MQGET call...
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Nov 21, 2015 7:45 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9405
Location: US: west coast, almost. Otherwise, enroute.

I just ran this test on a 7.5 MQ:
1. created new svrconn channel TEST.SVRCONN with DISCINT 30 seconds on QMCTEST qmgr
2. created local queue QL.A
3. set MQSERVER=TEST.SVRCONN/tcp/(1414)
4. ran amqsputc QL.A TEST QMCTEST
5. typed some meaningless data in amqsputc prompt
6. pressed enter; left the amqsputc waiting on STDIN
7. displayed channel status - TEST.SVRCONN in RUNNING state
8. waited more than 30 seconds - channel still in RUNNING state
9. typed some meaningless data into amqsputc and pressed enter key
10. amqsputc ends with 2009 r/c
11. displayed channel status - disconnected (INACTIVE) state

Here is a snapshot of my complete amqsputc interaction:

Quote:
C:\Documents and Settings\Administrator>AMQSPUTC QL.A QMCTEST
Sample AMQSPUT0 start
target queue is QL.A
MSG WITH SVRCONN SET TO DISC IN 30 SECONDS
AFTER 30 SECONDS
MQPUT ended with reason code 2009
MQCLOSE ended with reason code 2009
MQDISC ended with reason code 2009
Sample AMQSPUT0 end

C:\Documents and Settings\Administrator>

Quote:
DIS CHs(TEST.SVRCONN) ALL
7 : DIS CHs(TEST.SVRCONN) ALL
AMQ8417: Display Channel Status details.
CHANNEL(TEST.SVRCONN) CHLTYPE(SVRCONN)
BUFSRCVD(6) BUFSSENT(5)
BYTSRCVD(2032) BYTSSENT(1832)
CHSTADA(2015-11-21) CHSTATI(10.46.35)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.58.128) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(0000035C00000A8C) LOCLADDR( )
LSTMSGDA(2015-11-21) LSTMSGTI(10.46.42)
MCASTAT(RUNNING) MCAUSER(Administrator)
MONCHL(OFF) MSGS(3)
RAPPLTAG(s\c\Samples\Bin\amqsputc.exe)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(RECEIVE)
CURSHCNV(1) MAXSHCNV(10)
RVERSION(07050000) RPRODUCT(MQCC)


Aha!

After DISCINT expires, the DISPLAY CHSTATUS for the channel still shows RUNNING as the amqsputc program is still waiting for me to type the next message. When I type the next msg or press enter on a null line, then the CHSTATUS goes INACTIVE.

Is this the issue you see?

If so, what is the HBINT (heartbeat interval) for the SVRCONN channel? The initial value from the SYSTEM.DEF.SVRCONN definition is 300 seconds (5 minutes).

I set DISCINT to 30 seconds on my TEST.SVRCONN channel, and re-ran the test. The channel went INACTIVE in 30 seconds. When I next pressed enter on the amqsputc program, I received the 2009 r/c.

Try setting DISCINT to a lower value, and re-run your test.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
depuk
PostPosted: Mon Nov 23, 2015 4:06 am    Post subject: Reply with quote

Apprentice

Joined: 13 Nov 2015
Posts: 31

Thanks Bruce,
Eariler i fallowed upto 8 th step to test my scenario with DISCINT 300 seconds but my SVRCONN channel was not closing after 300 sec .Now i changed DISCINT to 30 seconds and tested now my server channel is closing after 30 sec. HBINT interwal is 300 sec.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » MQ client connection channel is not closing
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.