| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [SOLVED]Test on WF behavior |
« View previous topic :: View next topic » |
| Author |
Message
|
| CHF |
 Posted: Thu Apr 22, 2004 10:05 am Post subject: [SOLVED]Test on WF behavior |
 |
|
Master
Joined: 16 Dec 2003
Posts: 297
|
I have performed the following test:
No. of initial Execution Server Instances running = 4
Test1: A ProcessTemplateCreateAndStartInstance XML message was put to WF EXEXMLINPUTQ, specifying an undefined Queue name for Reply2Q.
Result: All the 4 Execution Server Instances were down. The message is still in EXEXMLINPUTQ. When the Execution Server was brought back manually, immediately one instace of the Execution Server went down.
No. of Execution Server Instances running = 3 (at this time)
Workflow discarded that message from the EXEXMLINPUTQ.
Test2: The same ProcessTemplateCreateAndStartInstance XML message was put to WF EXEXMLINPUTQ again, specifying an undefined Queue name for Reply2Q.
Result: The remaining 3 Execution Server Instances running at that time were down. When the Execution Server was brought back manually, immediately two instaces of the Execution Server went down.
No. of Execution Server Instances running = 2 (at this time)
Workflow discarded that message from the EXEXMLINPUTQ.
Does anybody have any idea on why Workflow tried to process the message 5 times?
Thanks
CHF 
Last edited by CHF on Mon Apr 26, 2004 10:07 am; edited 1 time in total |
|
| Back to top |
|
 |
| CHF |
| Posted: Thu Apr 22, 2004 10:13 am Post subject: |
|
|
Master
Joined: 16 Dec 2003
Posts: 297
|
This is from the Programming Guide Manual:
| Quote: |
Errors when returning a response: When an XML response message is put into an MQSeries queue, an error can occur, for example, when the specified queue is undefined or when that queue is full.
When putting the response into the reply queue fails, the error and the first 500 bytes of the response are logged into an error log. The original XML message is committed and thus removed from the input queue. All put errors are assumed to be permanent, that is, it is assumed that all subsequent puts will also fail. Therefore, processing of the incoming message is not retried. |
If this is true, that means WF tries to process a response message only once. But Why did WF tried to process the message 5 times?
Thanks
CHF |
|
| Back to top |
|
|
| mqworkflow |
| Posted: Thu Apr 22, 2004 11:53 am Post subject: 5 times retry |
|
|
Apprentice
Joined: 23 Feb 2004
Posts: 32
|
Check for the following in your FDL
MESSAGE_RETRY_LIMIT 5
If you find this in the FDL you have now in the RTDB, it means you asked the workflow..actually MQ to retry to play the messages five times. This is the default value. You can change this value to any reasonable no you want.
Hope this answers why the message was tried 5 times.
BTW, just curious to know how you came to the conclusion that messages are being played only 5 times by observing the killing of exec servers.
Thanks |
|
| Back to top |
|
|
| CHF |
| Posted: Thu Apr 22, 2004 12:12 pm Post subject: |
|
|
Master
Joined: 16 Dec 2003
Posts: 297
|
| Quote: |
| BTW, just curious to know how you came to the conclusion that messages are being played only 5 times by observing the killing of exec servers. |
I am working on OS/390. In OS/390, WF dies everytime it tried to put a Reply message to Reply2Q (Which was undefined for testing purpose). |
|
| 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
|
|
|
|
