This discussion is archived
4 Replies Latest reply: Nov 11, 2013 11:11 PM by MSRaghava RSS

BPEL Instance error on assignment.

Sujan Kumar Paidiapala Newbie
Currently Being Moderated

Hi All,

 

we are facing an issue on production.

After receiving data from B2B adapter trying to assign the payload to some other variable. Transaction is getting faulted in this assignment and it dont show us the selection failure here. Error we see in instance is

 

<exception  class="com.collaxa.cube.engine.EngineException">

Variant not found. The variable "" is not declared in the current scope. All variables must be declared in the scope before being accessed. This was an internal error. The flow was not generated correctly by the BPEL compiler. Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

<stack>

<f>com.collaxa.cube.engine.core.Scope.getVariantRV#585</f>

<f>com.collaxa.cube.engine.core.Scope.getAsObjectRV#575</f>

<f>com.collaxa.cube.engine.core.Scope.getAsObject#881</f>

<f>com.collaxa.cube.engine.ext.bpel.common.BPELWMPHelper.evalFromValue#375</f>

<f>com.collaxa.cube.engine.ext.bpel.v1.wmp.BPEL1AssignWMP.__executeStatements#138</f>

<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>

<f>com.collaxa.cube.engine.CubeEngine.performActivity#2688</f>

<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1191</f>

<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>

<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#78</f>

<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>

<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>

<f>com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke#608</f>

<f>com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke#296</f>

<f>sun.reflect.GeneratedMethodAccessor1665.invoke</f>

<f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>

<f>...</f>

</stack>

</exception>





for the same issue, when we look in the logs found below logs.


<Oct 17, 2013 10:24:50 AM EDT> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-000000> <Failed to handle dispatch message ... exception ORABPEL-05002


Message handle error.

error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Variant not found.

The variable "" is not declared in the current scope. All variables must be declared in the scope before being accessed.

This was an internal error. The flow was not generated correctly by the BPEL compiler.

Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).


This error contained an exception thrown by the message handler.

Check the exception trace in the log (with logging level set to debug mode).


ORABPEL-05002


Message handle error.

error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Variant not found.

The variable "" is not declared in the current scope. All variables must be declared in the scope before being accessed.

This was an internal error. The flow was not generated correctly by the BPEL compiler.

Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).


This error contained an exception thrown by the message handler.

Check the exception trace in the log (with logging level set to debug mode).


        at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)

        at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)

        at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:887)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)

        at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)

        at java.lang.Thread.run(Thread.java:662)

>



this fault is happening for some of the transactions only. not for all the instances.

As its not getting caught by catch block, bpel engine is retrying on BPEL engine recovery time, thats causing issue on servers.


Please suggest a solution for the above problem.


Regards

Vicky.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points