| Author |
Message
|
| dg_sl_uk |
 Posted: Sat Jan 10, 2004 2:15 am Post subject: [SOLVED] UPES activity stalling in "running" state |
 |
|
Newbie
Joined: 09 Jan 2004
Posts: 5
Location: United Kingdom
|
Hi,
I have a simple MQSW flow with two activites. The first is a UPES activity which is set to run synchronously.
The problem I'm having is that, on the return to workflow from a successful UPES run, the flow is not advancing to the next activity - and the process instances for my activity is staying in a running state.
All of my tracing tells me that the message has gone to the right queue okay. All return/condition codes are 0. The message is definately on the EXE.XML queue and all the right info is there.
For reasons I don't understand, MQSW appears not to acknowledge the response sitting in the EXE.XML queue.
Has anyone else seen this ? Do you have any suggestions on how to solve this ?
Thanks in advance for any assistance.
Dave
Last edited by dg_sl_uk on Tue Jan 13, 2004 6:29 am; edited 1 time in total |
|
| Back to top |
|
 |
| jmac |
| Posted: Sat Jan 10, 2004 6:10 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
It seems to me that you are probably not sending a properly formated ActivityImplInvokeReply message. Have a look in your fmcsys.log file and you will probably see an error message.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| dg_sl_uk |
| Posted: Mon Jan 12, 2004 1:48 am Post subject: |
|
|
Newbie
Joined: 09 Jan 2004
Posts: 5
Location: United Kingdom
|
Thanks for that John,
I checked out the fmcsys.log and didn't see any errors along those lines. However, I did an export of the fdl file from runtime and found that there were 2 Queue managers listed.
Could this perhaps explain why my UPES response is
- either is not reaching MQSW
- or, if it is reaching MQSW, is not being accepted as a response (and
changing Activity state from Running to Finished).
As ever, thanks in advance for any advice.
Dave |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 12, 2004 5:18 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Dave:
I have no experience with anything like you explain... but I would say you should delete the QM that is not being used... check the SYSGROUP definition (I believe thats where the QM name is stored).
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jan 12, 2004 7:35 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Is your PUT successful for sure? If yes, post the response XML you are sending back to workflow. |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jan 12, 2004 7:59 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
WF must be rejecting your XML. check your defined "ReplyTo" queue for any error messages.
_________________
-Ratan |
|
| Back to top |
|
|
| dg_sl_uk |
| Posted: Tue Jan 13, 2004 6:29 am Post subject: |
|
|
Newbie
Joined: 09 Jan 2004
Posts: 5
Location: United Kingdom
|
Thanks for your advice folks, but it has turned out that it was an incorrect Queue definition on the manframe that was our culprit.
It was set to Trigger on "Every" rather than "First", and got stuck the first time an erronious message was lodged there.
At least thats how our m/f guys explained it to me !
Cheers,
Dave
|
|
| Back to top |
|
|
|
|
