| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to disconnect Client channels |
« View previous topic :: View next topic » |
| Author |
Message
|
| ckelly |
 Posted: Thu Jan 20, 2005 10:05 am Post subject: How to disconnect Client channels |
 |
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
Hello
I have a system where a developer has produced dodgy code and is not disconnecting their client connections properly, I know about increasing the number of active channels, I don't particularly want to do that and I don't want to bounce the qmgr either if I can help it.
The code will be fixed but for now can anyone tell me how I can get rid of the client connections rather than just stopping them?
Any help would be much appreciated
thanks
ck |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Thu Jan 20, 2005 10:21 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Asside from having the developer fix the dodgy code the only way I know of is to issue a "stop chl(CHANNEL.NAME) mode(force) status(inactive)". But if you do it that way and the application hasn't been coded to re-connect it will have to be bounced.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jan 20, 2005 12:30 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Check out Support Pack ME71, an exit that limits the # of channels spawned off of a SCRCONN. And next time you talk to IBM, ask that this functionality is made part of the base product.
I made a formal request for this:
| Quote: |
>>>Limit Number of WMQ Client Connections at Channel Level
Recognised- IBM agrees with the request and a solution appears to be a desirable objective. A solution, however, may not presently appear feasible or implementable. No IBM commitment is made or implied as to the eventual delivery of an acceptable solution.
This is a candidate feature for a future version of WMQ. It will not be part of the next release, but is being considered for the version after that. Adding this to the base product requires new attributes on objects which in turn requires lots of further extensions and migration code. Hence this would be something done at a release boundary, not added in the service stream for existing versions.
|
But the only way to get rid of existing ones is what Chris said. Stop the channels. Or stop the QM.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ckelly |
| Posted: Fri Jan 21, 2005 1:29 am Post subject: |
|
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
Hi
Thanks for your replies.
I did stop the channels but then the app was getting errors as that actually doesn't get rid of the connections. I ended up deleting the svrconn channel and recreating it, this set the wheels of messaging in motion again!
ck |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 21, 2005 3:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did you stop mode(force) status(stopped) or just stop ?
You should not have to delete and recreate the channel.
Enjoy  |
|
| 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
|
|
|
|
