| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FMC31050E Error from Workflow Trigger |
« View previous topic :: View next topic » |
| Author |
Message
|
| tdwells |
 Posted: Thu Aug 07, 2003 11:13 am Post subject: FMC31050E Error from Workflow Trigger |
 |
|
Apprentice
Joined: 30 Oct 2002
Posts: 42
|
All,
Just thought this was interesting enough to post.
I have a Java application that pulls financial information from an Oracle table and puts the data into workflow in the EXEXMLINPUTQ using XML.
Of course, one of the values pulled is an amount whereby I used the following command in my select sql:
to_char(line_amount, '9999999999999.00PR').
The actual value being pulled from the Oracle table was a negative amount, but since I used the 'PR' in the to_char command, Oracle was returning <300.00> rather than -300.00.
Therefore the XML being produced and input into Workflow was something like <amount><300.00></amount>
When Workflow would receive the request in EXEXMLINPUTQ, the Workflow trigger monitor was failing giving the following error information:
FmcFMLException in OpenQueue, ReasonCode = 2087
FMC31050E An error occurred which has terminated processing.
FMC10200I Execution server for system FMCSYS started.
When I changed the select sql command to the following:
to_char(line_amount, '9999999999999.99'), the problem went away and Workflow began processing the request properly.
FYI
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Aug 07, 2003 11:57 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Can you confirm the two things ( data in the XML message and the workflow exec server abending) are related.
Can you recreate the problem?
I saw that if the UPES Queue is not defined (and hence 2087) then the workflow exec server abends. This is fixed in one of the service packs. But now, you are telling me that some XML data is causing the exec server to abend. If you can recreate the problem, then IBM would love to know about it and would add it to their bug list and fix it in the next release of their SP. |
|
| Back to top |
|
|
| tdwells |
| Posted: Thu Aug 07, 2003 12:33 pm Post subject: |
|
|
Apprentice
Joined: 30 Oct 2002
Posts: 42
|
I was able to re-create the problem. Here is the error that the MQ trigger monitor produced for the FMCTRIGGER queue when I submitted a request.
/var/fmc/cfgs/FMC/bin/fmczemst 'TMC 2 FMC.FMCGRP.FMCSYS.PROC.EXE /var/fmc/cfgs/FMC/bin/fmczemst & -i:ExeSvr -y:FMC FMCQM '
FmcFMLException in OpenQueue, ReasonCode = 2087
08/07/03 15:25:42 FMC31050E An error has occurred which has terminated processing.
FMC10200I Execution server for system FMCSYS started.
When I changed the select sql command back to use -300.00 rather than <300.00>, the Workflow process was properly accepted and started. Further, there was no error from the trigger monitor.
_________________
IBM Certified Specialist - MQSeries |
|
| 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
|
|
|
|
