| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SVRCONN Channel in STOPPING State |
« View previous topic :: View next topic » |
| Author |
Message
|
| EddieA |
 Posted: Tue May 16, 2006 8:29 am Post subject: SVRCONN Channel in STOPPING State |
 |
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Hi,
Noticed on one of our systems that we have a SVRCONN Channel in a STOPPING state and it's been like that for a number of days. Looking at the status of the channel, I can see 3 Current connections, all in a STOPPING state. The last message date/time on each of these connections are more than a month old, so my guess is that the connectiong system crashed in some way, or for whatever reason didn't gracefully close these out. My next guess, is that someone tried to STOP the channel, to release these connections, but it 'ain't working.
So, short of bouncing the QM, is there any way to clear up these channel connections.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue May 16, 2006 8:36 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
stop channel mode(force)
stop channel mode(terminate) |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue May 16, 2006 8:40 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
I do not think either of those will work. The channel already knows that it has to stop, but it is probably still waiting for a chance to do so. I would guess that the thread is stuck in a TCP call, and has not returned to WMQ code yet. Attach a debugger to the channel PID to see what it is doing.
You could check the PID of the process running the channel, JOBNAME in DIS CHS(CHL), and kill that process. Of course, if it is the channel pool process you will blow away all other channels running in the same process.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue May 16, 2006 8:55 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Nigel, thanks, but I don't think it would be appreciated if I killed the task that ALL the channels were using. 
Vennela, thanks, thanks, thanks. The mode(force) changed the status to STOPPED. Then an alter with status(inactive) cleared out the, now, stopped connections. Next time you're in L.A. I'll buy you a beer.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| vennela |
| Posted: Tue May 16, 2006 9:56 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| EddieA wrote: |
| Next time you're in L.A. I'll buy you a beer. |
Last time didn't work ah. Next time definitely
But this won't work for some other channels. If you do that for SDR channel, and then start it back again, then it says the XMITQ is still in use. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue May 16, 2006 4:53 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| vennela wrote: |
| But this won't work for some other channels. If you do that for SDR channel, and then start it back again, then it says the XMITQ is still in use. |
I never have that problem when stopping SNDRs even with FORCE.....
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
