| Author |
Message
|
| velocity |
 Posted: Tue Nov 30, 2010 8:57 am Post subject: Deleting local queues with processes attached to it |
 |
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
Hi Guys, I am not able to delete a local queue since some processes are attached to it (amqrmppa, etc). Is there a way to delete this queue without bouncing the queue manager?
Please let me know.
Regards, |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Nov 30, 2010 9:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Why did you post this to the Security forum?
What have you tried? What options exist on the DELETE command?
What options do you have to identify the processes using this queue, and then what options do you have to cause those processes to remove their open handles? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 30, 2010 9:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to relevant forum
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 30, 2010 9:08 am Post subject: Re: Deleting local queues with processes attached to it |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| velocity wrote: |
| Hi Guys, I am not able to delete a local queue since some processes are attached to it (amqrmppa, etc). Is there a way to delete this queue without bouncing the queue manager? |
Yes. What have you tried apart from the delete button on MQExplorer and posting in the wrong section of this forum?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| velocity |
| Posted: Tue Nov 30, 2010 9:18 am Post subject: |
|
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
Sorry to post this in a wrong forum.
amqrmppa is the only process attached to the queue. I am afraid killing this process would affect other applications.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 30, 2010 9:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| velocity wrote: |
| amqrmppa is the only process attached to the queue. I am afraid killing this process would affect other applications.. |
And what does this process do? What would be the likely impact of killing it? Given what it does, what other actions aside from a kill -9 would be likely to stop it / cause it to release the handle on the queue?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rnikula |
| Posted: Tue Nov 30, 2010 6:48 pm Post subject: process using the queue |
|
|
Newbie
Joined: 30 Nov 2010
Posts: 2
|
| The process name you indicated, amqrmppa is a process associated with an MQ channel. If the channel has not released the queue, you should be able to stop and restart the channel to free it up. I wouldn't advise killing the process, but if you do, MQ should recover from it. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 30, 2010 7:01 pm Post subject: Re: process using the queue |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| rnikula wrote: |
| The process name you indicated, amqrmppa is a process associated with an MQ channel. If the channel has not released the queue, you should be able to stop and restart the channel to free it up. I wouldn't advise killing the process, but if you do, MQ should recover from it. |
Excellent first post.
Really well done.
Thank you.
Congrats.
Absolutely no sarcasm. Please, stick around. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Wed Dec 01, 2010 2:26 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
If the channel services more than just the one queue, you will kill all connections when you stop the channel.
To identify the connection specific to this particular queue, use the 'dis conn' command with a filter to identify the specific connection to that queue (object).
Then, kill that specific connection (stop conn).
I do strongly suggest you read about 'dis conn', 'stop conn' and filters before trying this. If your filter statement is incorrect, you may kill the wrong connection.
Sadly, we find we need to do this way too often with misbehaving applications in development.
(And, welcome rnikula.) |
|
| Back to top |
|
|
|
|
