| Author |
Message
|
| griffel |
 Posted: Thu Apr 28, 2005 5:19 am Post subject: Resolve invisible (locked) message from MQI channel |
 |
|
Novice
Joined: 22 Mar 2005
Posts: 23
|
Is there any chance to unlock messages that originally where put via JMS's underlying MQI channels (SVRCONNs) and got "invisible" due to poisoned message - already removed - without restarting the queue manager itself?
I think any kind of RESOLVE CHANNEL isn't applicable to MQI channels.
The configuration used is a MQ 530 CSD9 Windows client JMS program
connected to a 531 z/OS 1.6 MQ via SLLed SVRCONNs.
Any help out there? |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Apr 28, 2005 7:16 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
What are you trying to say
Atleast, I didn't understand the question |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Apr 28, 2005 7:46 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I think he is saying that he had some poison messages moved to his backout queue and he wants to know how to get them back? |
|
| Back to top |
|
|
| griffel |
| Posted: Thu Apr 28, 2005 8:25 am Post subject: |
|
|
Novice
Joined: 22 Mar 2005
Posts: 23
|
Sorry, I like complex questions for complex(?) problems 
What I want to know is: How can I make my messages visible again (that's getting the QM to free his lock).
Those message are locked, since the QM decided to freeze further MQGETs on a queue with a poisoned message.
Now, if I had a configuration with QM-to-QM communications or
CICS or IMS involved, I simply would do some RESOLVE CHANNEL
stuff.
But since I only have a poor MQI channel connected to my JMS client,
I have no idea, how to resolve my message without restarting the whole QM - which definitely works (during restart it resolves all indoubts and locks corretly, and afterwards, my queue are filled up with the formerly invisible messages). But I can't restart our production systems that simple. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 28, 2005 11:09 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So this is really a poison message problem.
Well if you do have a poison message on your queue you will have to move it.
Manual move would be to a backout queue.
Automatic move (WAS) to either a backout queue or the DLQ.
Make sure you set the back out threshold on the queue in order to avoid the poison message stopping your processing. You will have to act on it in your application (non WAS) or let WAS do the handling of the poison message.
Enjoy  |
|
| Back to top |
|
|
| griffel |
| Posted: Fri Apr 29, 2005 12:33 am Post subject: |
|
|
Novice
Joined: 22 Mar 2005
Posts: 23
|
| Quote: |
| So this is really a poison message problem. |
No, it is not - it is a _result_ of posinoned messages occuring.
(sorry, my question seemed to be rather "compressed")
My only problem is, how to get in touch with messages that
were process at the time some poisoned messages broke
the overall processing.
The poisoned messages, have been removed immediately.
Thus, all messages that arrived afterwards got processed correctly.
But I don't want to restart the whole QM to resolve the "invisible"
messages being, if there's any chance to avoid it. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 29, 2005 3:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So basically, it seems you have uncommitted messages in your queue.
You're looking for a way to resolve the uncomitted status of these messages.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| griffel |
| Posted: Fri Apr 29, 2005 5:01 am Post subject: |
|
|
Novice
Joined: 22 Mar 2005
Posts: 23
|
| Right. I shaped my original question a bit more complex, since asking the concerned queues about their status gave UNCOM(NO). After a QM-restart definitely appeared a couple of hundred messages again (those I missed). |
|
| Back to top |
|
|
|
|
