A sent transaction gives the following error message and no details are given against the recipients:An Error Occurred In The Send Notice BPEL Process
This error means that a problem has occurred which the web server can’t interpret as a specific error message, which would normally be defined in the EToN Fault Reason element. The only way to diagnose this is to log in to the BPEL console on the web server and see what is happening when transmitting that transaction:1 - Log into the BPEL console as the OC4JADMIN user2 - Select the correct domain if you have multiple (I.E. Live/Test or different organisations) else leave as default3 - Click on the Instances tab4 - Using the Modified Datim on the TMA3000 form for the problem transaction, search through the list of instances for around the same time.5 - Click on an instance you suspect is the one for your problem transaction6 - Click on the Flow tab7 - In the flow find the blue Invoke_get_notice_xml stage and click on it8 - Read through the XML and check that it is the XML of the problem transaction you are investigating. If it isn't go back to the list of instances and try another from around the same time. If it is the correct notice then close the window anyway and continue to the next stage.9 - Look through the flow and see if any of the stages are highlighted in red. The problem normally occurs on the Invoke_EToN stage but could occur at a different point. If none are highlighted in red then select the Invoke_EToN stage.10 - Browse through the XML conversation and see if any errors are shown which may highlight the problem.
One example of a problem where this error occurred is when an invalid response was received from the recipient web server – the XML of the response was invalid.Here is an example of what our correct response looks like for a transaction:<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://www.wrcplc.co.uk/Schemas/ETON"> <env:Body> <ns0:EToNrequestResponse SchemaVersion="5.0"> <ns0:ProcessDatim>2011-03-23T16:56:53.000+00:00</ns0:ProcessDatim> </ns0:EToNrequestResponse> </env:Body></env:Envelope>
Here is an example of what a web service gave back which contained an invalid ProcessDatim:<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:ns1="http://oystertechnology.org.uk/server/eton/xml/eton.wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:enc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <env:Body xmlns:rpc="http://www.w3.org/2003/05/soap-rpc"> <ns1:EToNrequestResponse env:encodingStyle="http://www.w3.org/2003/05/soap-encoding"> <rpc:result>return</rpc:result> <return xsi:type="enc:Struct"> <ProcessDatim xsi:type="xsd:string">2011-03-23T17:55:17</ProcessDatim> </return> </ns1:EToNrequestResponse> </env:Body></env:Envelope>Problem 60712
Product TechNotes and FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!