| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Workflow dumping bad messages onto HOLDQUEUE |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqmaniac |
 Posted: Mon Nov 06, 2006 5:39 pm Post subject: Workflow dumping bad messages onto HOLDQUEUE |
 |
|
Master
Joined: 27 Dec 2005
Posts: 201
|
Hello Everyone,..
I am having hard time figuring out on why/When does Workflow duump messages onto its HOLD queue.
I sent 50 messages to workflow and see all the 50 instances generated on the server.BUT,..Only 30 of them generated user workitems.
Even though the rest generated the Instances they are still in start state and did not go through the first activity.
I see 20 of them in the start state.
and 20 messages dumped onto the EXEHOLDQ.
I am confused on how to deal with these Hold queue.should the admins manually move these mesaes or will workflow take care of these automatically.
I see message backout errors on the server.
Should the admins manually move the messages back at a later time.
Any Thoughts/Suggestions/Books...Pls Help!! |
|
| Back to top |
|
 |
| hos |
| Posted: Tue Nov 07, 2006 12:50 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
MQWF puts only server messages onto the hold queue. Any client request message just times out and the client gets an API_TIMEOUT_ERROR.
Server messages are put onto the HQ when processing and several processing retrys failed due to an error - usually a DB problem.
Before you can replay the HQ messages you need to evaluate the root cause of the failure. Check the system log and the error log for error messages preceeding the message that the message was put onto the HQ. Make sure that this error is fixed (e.g. a wrong UPES queue definition) and the replay the HQ messages with the admin utility (fmcautil). First replay only one by one. If everything works fine, you may replay the whole message queue.
You did not mention the MQWF version. There were a couple of deadlock fixes in the past that you need to apply in order to avoid hold queue messages.
Good Luck! |
|
| Back to top |
|
|
| mqmaniac |
| Posted: Tue Nov 07, 2006 2:31 pm Post subject: |
|
|
Master
Joined: 27 Dec 2005
Posts: 201
|
Thanks for the reply,
I am using MQWF 3.5 on Z/Os System.when we tried to replay the mesages Its failing again.
Can you tell me the atest deadlock fixes available. |
|
| Back to top |
|
|
| hos |
| Posted: Wed Nov 08, 2006 12:11 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
1. Once again: you need to figure out the root cause for the failing message.
Check FMCERRxx of your server joblog to find out and fix the root cause.
2. Any MQWF fixes are shipped via SupportPacs The latest SupportPac
available for MQWF 3.5 is SP#7. Contact the IBM Support to obtain a
SupportPac. However it is very unlikely that the root cause of your
problems is a deadlock, as the problem persists when you replay the
message. |
|
| 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
|
|
|
|
