| Author |
Message
|
| prKinch |
 Posted: Mon Jul 05, 2010 9:59 am Post subject: How to stop the connections of server connection channels |
 |
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
Hi
I tried to stop the svrconn channel... And channel went to stopped status, But when i check the chstatus of the svrconn channel. The connections were in stopping status, And When i start the channel the coneections are in running status.
I need to close all open connections in the channel.. Is there any specific commands for this? This in Solaris box |
|
| Back to top |
|
 |
| prKinch |
| Posted: Mon Jul 05, 2010 10:14 am Post subject: |
|
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
And,,, I got this command from MQ Books
STOP CONN STOP CONN(connection-identifier)
I dont know how to find the connection-identifier for the connections
I tried to give the connection-identifier value as
1) CONNAME(16.24.95.3)
2)JOBNAME(0000112D00000082)
But I am unable to close the connections....
Pls advise
AMQ8417: Display Channel Status details.
CHANNEL(LAFS.GLF.CLNT) CHLTYPE(SVRCONN)
BUFSRCVD(25) BUFSSENT(24)
BYTSRCVD(14756) BYTSSENT(5648)
CHSTADA(2010-07-05) CHSTATI(06.24.2
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(16.24.95.3) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(0000112D00000082)
LOCLADDR(::ffff:116.24.95.11(1472))
LSTMSGDA(2010-07-05) LSTMSGTI(07.16.05)
MCASTAT(RUNNING) MCAUSER(tglgd01)
MONCHL(OFF) MSGS(22)
RAPPLTAG(WebSphere MQ Client for Java)
RQMNAME( ) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(STOPPING) STOPREQ(YES)
SUBSTATE(RECEIVE) XMITQ( ) |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Jul 05, 2010 10:24 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| prKinch wrote: |
And,,, I got this command from MQ Books
STOP CONN STOP CONN(connection-identifier)
I dont know how to find the connection-identifier for the connections
I tried to give the connection-identifier value as
1) CONNAME(16.24.95.3)
2)JOBNAME(0000112D00000082)
But I am unable to close the connections....
Pls advise
AMQ8417: Display Channel Status details.
CHANNEL(LAFS.GLF.CLNT) CHLTYPE(SVRCONN)
BUFSRCVD(25) BUFSSENT(24)
BYTSRCVD(14756) BYTSSENT(5648)
CHSTADA(2010-07-05) CHSTATI(06.24.2
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(16.24.95.3) CURRENT
EXITTIME(0,0) HBINT(300)
JOBNAME(0000112D00000082)
LOCLADDR(::ffff:116.24.95.11(1472))
LSTMSGDA(2010-07-05) LSTMSGTI(07.16.05)
MCASTAT(RUNNING) MCAUSER(tglgd01)
MONCHL(OFF) MSGS(22)
RAPPLTAG(WebSphere MQ Client for Java)
RQMNAME( ) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(STOPPING) STOPREQ(YES)
SUBSTATE(RECEIVE) XMITQ( ) |
connection is not same as channel though connection is made through it. Look at the follwoing url. I hope you will find your answer.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaj.doc/sc11950_.htm
Last edited by jeevan on Mon Jul 05, 2010 3:44 pm; edited 1 time in total |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Jul 05, 2010 1:34 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
To identify the many "conn" associated with a particular channel, try this:
dis conn(*) where(channel eq LAFS.GLF.CLNT)
This will display all the connections from that channel. The display will look like this:
| Code: |
AMQ8276: Display Connection details.
CONN(4BFD92C526995E01)
EXTCONN(414D5143434D47313032513039202020)
TYPE(CONN)
CHANNEL(LAFS.GLF.CLNT) |
There may be many of these.
To completely kill the channel, use the CONN identifier and stop each instance:
| Code: |
| stop CONN(4BFD92C526995E01) |
It is tedious (though not too bad if you copy and paste the CONN identifier). But that channel will be gone. |
|
| Back to top |
|
|
| prKinch |
| Posted: Mon Jul 05, 2010 4:01 pm Post subject: |
|
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
Yes I tried this,,, But still the connections are exist.
I stopped all the connections of the channel.By using stop conn (xxxx)
But When i display the channel, Still I can see the connections are in stopping status
And I cant see some connections display conn (xxxX) output
AMQ8276: Display Connection details.
CONN(4AA505AC20F83602)
EXTCONN(414D517517518545303030303020202020)
TYPE(CONN)
dis CONN(4AA50EC3DCA83602)
25 : dis CONN(4AA50EC3DCA83602)
AMQ8461: Connection identifier not found.
The logs in queue manager is not updated.Will this is normal? Or the log will be update |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jul 05, 2010 4:57 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| The logs in queue manager is not updated. |
What do you mean by this? Which log(s)? The error logs?
What kind of update to the logs would you expect?
_________________
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 |
|
|
| fjb_saper |
| Posted: Mon Jul 05, 2010 5:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Stop conn will kill the connection but not prevent the application from creating a new one.
If you truly need to shutdown the specific SVRCONN channel lookup the STOP CHL command with its different modes. Caution use mode(terminate) only under severe duress. It also kills the channel process on the OS.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| prKinch |
| Posted: Tue Jul 13, 2010 4:46 pm Post subject: Hi |
|
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
When we stop the connections, Will this update on the log ../mqm/qmgrs/errors log
When I stopped the connections and channel, the logs didnot get updated
We found that there is some problem in the channel.. And re-configured the channel again. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 13, 2010 4:50 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| We found that there is some problem in the channel.. And re-configured the channel again. |
Exactly what problem in the channel? How did you determine this? Was the problem with the SVRCONN definition? Something else?
Exactly what do you mean by "re-configured it?"
_________________
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 |
|
|
| prKinch |
| Posted: Wed Jul 14, 2010 2:56 pm Post subject: Hi |
|
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
We have deleted the serever connection channel and created a new one.
I stop the connections to the channels...The connection is not dropped properly when the dis connect period ended. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 14, 2010 2:59 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The connection is not dropped properly when the dis connect period ended.
Please, oh please, be precise. I/we have no idea what lead you to the conclusion that the connection not dropped properly.
Was there an error message on the error logs? Some other event? What commands did you use? What did you see? Where did you see it?
_________________
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 |
|
|
| bruce2359 |
| Posted: Wed Jul 14, 2010 3:52 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
This arrived as a PM:
| Quote: |
From: prKinch
To: bruce2359
Posted: Wed Jul 14, 2010 3:37 pm
Subject: REG How to stop the connections of server connection channel
I got this message from Mq tech. team
I am from MQ support team and I dont have much information.
Mq Tech. team gave this info only |
(I don't usually reply privately to PMs unless there is some proprietary or confidential issue.)
I gather from your PM that there is a distinction between MQ Tech team and MQ Support team; and that the two teams don't work cooperatively as a unit. I've worked in this type of environment, so I am sympathetic. I gather, as well, that you are new to MQ. Again, I am sympathetic.
That said, terms like "not working," and "not dropped properly," do not provide us with information useful for problem-determination.
_________________
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 |
|
|
| fjb_saper |
| Posted: Wed Jul 14, 2010 4:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
When using MO71 support tool and display "channel status List" look at last msg date and last msg time on the channel. If this timestamp is old you may have what is known as an orphaned channel instance.
This may happen with a network disconnect/interruption that the application caught but never tried to close the old connection...
Use Stop chl mode=> force status=> stopped|inactive and it will force stop these orphaned channels.
When using status =>inactive you get by default the ip of the connections this command is going to affect (see MO71 stop chl pannel)
When using status => stopped it will affect all channel instances of that name from all machines.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| J.D |
| Posted: Sun Jul 18, 2010 10:04 am Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
Use this command to stop Channel and now you will see entries about channel stopped state in ../mqm/qmgrs/errors.
STOP CHL("chl name") MODE(FORCE)
_________________
IBM WebSphere MQ & WAS Administrator |
|
| Back to top |
|
|
|
|
