This article describes how to solve some common problems with BPEL
processes..
Why and when to perform this task
The following solutions can help you to debug problems with your
BPEL processes.
If you get the error EngineMissingReplyException,
this means that a process ended without performing a reply activity. This
will happen if the process throws an exception, but does not handle it. Such
exceptions are not passed up to the calling process, but the EngineMissingReplyException is
passed up as far as the Web client, the original exception that your process
threw is not visible because it is masked by what is effectively an unhandled-exception
exception. In a non-interruptible process, this error will trigger compensation
if compensation is enabled for the process.
This is a modeling
problem, you must catch all possible exceptions and perform a reply activity
before the process ends. You can do this by adding a Catch All fault
handler that always performs a reply. For more information about soling this
problem, refer to Technote 1165360
.
The administrative console will stop responding if you try to stop
a BPEL-based process application while it still has process instances.
Before you try to stop the application, you must stop the business processes
so that no new instances are created , and do one of the following:
Wait for all existing process instances to end in an orderly way.
Terminate and delete all the process instances.
Only then, can you stop the process application. For more information
about preventing this problem, refer to TechNote 1166009
.
Searchable topic ID:
t5_bpel Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2 http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/workflow/tasks/t5_bpel.html