Implement callback for an asynchronous BPEL process through Java

Question

Hi ,
I am trying to implement a callback functionality for an asynchronous BPEL process through java.
I found the code in the samples folder of SOA suite installation folder .
<SOA_HOME>\bpel\samples\tutorials\102.InvokingProcesses\rmi\com\otn\samples\async.
There is an AsyncInstanceWatchdog object which registers a callback object(in this case an object of AsyncCallbackImpl class) for a specific CONVERSATION_ID.
String convId = GUIDGenerator.generateGUID();
nm.setProperty(NormalizedMessage.CONVERSATION_ID, convId);
deliveryService.post(proc_name, "initiate", nm);
// register the callback
watchdog.registerAsyncCallback(convId, testAsyncHandler,
locator.getDomainAuth());
// start it
watchdog.start();
There is no problem till the last line. But once the BPEL process returns the control( does a callback), it throws the following error.
May 25, 2010 3:36:06 PM oracle.j2ee.rmi.RMIMessages EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
WARNING: Exception returned by remote server: {0}
ORABPEL-02118
Variant not found.
The variant "output" has not been declared in the current scope. All variants must be declared in the scope before being accessed.
Please check that the variant "output" is properly declared; otherwise there may be a misspelling in the name of the variant.
     at com.collaxa.cube.engine.core.Scope.getVariantRV(Scope.java:535)
     at com.collaxa.cube.engine.CubeEngine.getFieldValue(CubeEngine.java:2668)
For your reference the variable output is declared in the definition of AsyncCallbackImpl (which implements the IAsyncInstanceCallback interface).
There are 2 methods defined in the AsyncCallbackImpl class.
public void onResult(Map pResultMessage) {
System.out.println("called back! ");
Iterator iTest = pResultMessage.keySet().iterator();
while (iTest.hasNext()) {
String key = (String)iTest.next();
System.out.println(XMLHelper.elementToString((Element)pResultMessage.get(key)));
public String getVariableName() {
return "output";
The variable name is same given in the sample code. And the BPEL process returns variable named output. So the name should not be a problem.
Is it because of the scope of the variable.. If so, how do I change it.
Any help would be appreciated.
Edited by: saptarishi on May 25, 2010 4:24 PM
Edited by: saptarishi on May 26, 2010 4:45 PM

Answer 1

Solved it by some googling .... :)
Here is the link:-
[http://abhishek-soablog.blogspot.com/2008/09/orabpel-02118.html]
or
[http://beautifulwaste.blogspot.com/2008/04/calling-asynchronous-bpel-process.html]
Both gives the same solution..
In pre 10.1.3.3 release the default behaviour were to keep global variable information along with the instance information for completed BPEL processes.
In 10.1.3.3 or later, this behaviour changed for performance reasons so that the default behaviour is now, not to keep any global variables for a BPEL process once the BPEL process has completed.
You can configure this behaviour on a process level basis by using the parameter keepGlobalVariables in the bpel.xml file for the specific process:
<BPELSuitcase>
<BPELProcess src=".........." id="...........">
<configurations>
<property name="keepGlobalVariables">true</property>
</configurations>
</BPELProcess>
</BPELSuitcase>
Thanks
saptarishi