| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Advancing control of a UPEZ Task in Error. |
« View previous topic :: View next topic » |
| Author |
Message
|
| CSonn |
 Posted: Thu Jul 05, 2007 7:02 am Post subject: Advancing control of a UPEZ Task in Error. |
 |
|
Newbie
Joined: 03 Jul 2007
Posts: 3
|
We have a Task that sends a UPES to a service. That service sends an exception if a deadlock occurs for that UPES. This causes the Task to go into error. If this happens, We would like to retry the UPES message one more time after waiting 5 minutes and if that second UPES task fails, then we need that second UPES task to stay in error so we can manually look at the UPES message. We cannot figure out how to advance control from a task in error to the next task. Is there a way to advance control from a Task that is in error?
Thanks in advance
By the way, we are using WF 3.6... |
|
| Back to top |
|
 |
| hos |
| Posted: Thu Jul 05, 2007 10:37 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
you could consider to use expiration. If your UPES activity usually completes within seconds, you can model an expiration time of 5 Minutes for it and continue navigation to the second UPES activity when expiration takes place.
Have a look into the Buildtime Guide for more information about expiration. |
|
| Back to top |
|
|
| CSonn |
| Posted: Fri Jul 06, 2007 10:25 am Post subject: Advancing control of a UPEZ Task in Error. |
|
|
Newbie
Joined: 03 Jul 2007
Posts: 3
|
| Thanks for the reply. We have tried using expiration but the task's control will not advance. When the task goes "in error" the expiration time is ignored and the task remains in error. Is there anything else we can do? |
|
| Back to top |
|
|
| vijaycr |
| Posted: Sat Jul 07, 2007 8:01 pm Post subject: |
|
|
Acolyte
Joined: 11 Oct 2006
Posts: 62
Location: Singapore
|
Instead of sending an Exception from the UPES service. You could have an exit condition for the UPES activity and send back a successfull message which would satisfy the exit condition. In case of an error, you can send back an error message that would not satify the exit condition.
This will cause a workitem to be created in ready state, which can then expire.
We used a nonzero RC to indicate an error in 3.5 and it worked. |
|
| 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
|
|
|
|
