|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Messages locked in XMITQ |
« View previous topic :: View next topic » |
Author |
Message
|
matth |
Posted: Tue Feb 13, 2007 10:56 am Post subject: Messages locked in XMITQ |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
Hi:
(My first post in this forum)
I have an stable MQ enviromment running in Linux (WMQ 5.3 CSD12) and never had a problem with him. Today, I've seen a large number of messages stopped in an Transmission Queue (XMITQ). The queue had TRIGGER and de channels was up and running (Sender and Receiver). In despite this I've checked tcp connection with telnet. Channels were stop/started without success.
No log are generated in MQSeries global logs neither in MQSeries Instance (qmgrs) logs. No FFST was created too.
The MQSeries was restarted, but messages still stopping in transmition Queue. The server was rebooted too, but no success too.
I couldn't find any reason to explain this situation. I've tried to delete all messages in queue and recrate queue (maybe it's corrupted ???), but
commands CLEAR and DELETE QLOCAL wasn't worked.
I've recrated Queue definition. No error message as generated and Queue recreated still with messages in.
Finally, I've recreate all objects set (Remote Definitions, Transmission Queue and channels pair) and this appears to solve the problem. "Appear" because after too many unsucessfull tries, the Depth Count begins to decrease.
This Queue Manager had other sets of Transmission Queues to other places and no problem was found with these objets. Just one Transmission queue with messages to send.
Anyone has a explanation for this situation? No parameter of queue and channels was changed from installation date. This enviromment works since 2004, without changes.
Regard's |
|
Back to top |
|
 |
bbburson |
Posted: Tue Feb 13, 2007 12:25 pm Post subject: |
|
|
Partisan
Joined: 06 Jan 2004 Posts: 378 Location: Nowhere near a queue manager
|
Most likely the destination queue on the receiver end of your SDR channel is full (and messages are going to the remote DLQ if it's defined). When this happens the sender will back off and retry periodically until it can successfully put messages. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Feb 13, 2007 3:34 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
The other possibility I have seen ties to an ATG transaction manager and unfinished XA transactions.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
matth |
Posted: Wed Feb 14, 2007 7:55 am Post subject: |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
fjb_saper wrote: |
The other possibility I have seen ties to an ATG transaction manager and unfinished XA transactions.
Enjoy  |
And how I can see/manage these transactions? |
|
Back to top |
|
 |
matth |
Posted: Wed Feb 14, 2007 8:52 am Post subject: |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
bbburson wrote: |
Most likely the destination queue on the receiver end of your SDR channel is full (and messages are going to the remote DLQ if it's defined). When this happens the sender will back off and retry periodically until it can successfully put messages. |
I've tried to repeat the problem, simulating decreasing MaxDepth on receiver end. But some differences appear in this case:
-A error (9544) appears in log file in both sides.
-Messages go to DLQ as said.
-Messages are popped from Transmission Queue (in problem, message stays in transmission Queue).
-Messages don't go to qlocal on receiver-end, after queue is cleaned (after maxdepth can receive again the batch of messages). |
|
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
|
|
|
|