Posted: Wed Oct 20, 2010 6:13 am Post subject: Problem when Target subscribed queue is full
Voyager
Joined: 19 Dec 2005 Posts: 79 Location: India
Hi all,
I have a situation here... it's a pub/sub scenario and the target subscribed queue was full due the stopage of the listening application. Meanwhile, there were 1000s of unprocessed messages lying in the error queue. I tried to resend some of the messages and they went well.
Now I am trying to figure out why these messages were sent to error queue when they are not errenous. I can think of a reason being one as, since the subscribed queue was full and it couldn't hold anymore messages, these failed, but again I believe the messages should have instead processed by the flow and should have ended up in the dead-letter queue of the subscribed queue's queue manager. _________________ BR,
Deepak N
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Do you have something attached to the Catch Terminal of the InputNode?
If so does this eventually write data to the Error Queue?
If so then problem solved.
Try enabling user trace and sending a message to a full queue. Watch what Broker does when the MQOutput Node detects the queue is full. That will give you the answer why the messages end up on the error queue.
Now, make the error queue full. Then repeat. Where dow the message end up then.
This is all WMQ 101 stuff. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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