Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: failed to handle message ORABPEL-02182 Bpel
Log files:
BPEL logs :-
<2010-04-08 08:47:29,624> <ERROR> <clientprofile.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
ORABPEL-02182
JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "25010729-BpInv2-BpSeq0.3-3". The reason is The execution of this instance "25010729-BpInv2-B
pSeq0.3-3" for process "ApproveTask" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get mo
re information..
:Please consult your administrator regarding this error.
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.checkIfTransactionIsActive(BPELInvokeWMP.java:985)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:398)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:199)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3714)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1657)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:325)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5787)
at com.collaxa.cube.engine.CubeEngine.callbackPerformer(CubeEngine.java:1896)
at com.collaxa.cube.engine.delivery.DeliveryHelper.callbackPerformer(DeliveryHelper.java:865)
at com.collaxa.cube.engine.delivery.DeliveryService.handleCallback(DeliveryService.java:976)
at com.collaxa.cube.engi
Node 1 - domain.log :
5 processes have been loaded for BPEL domain "Support".
<2010-04-06 09:56:36,897> <ERROR> <declaration.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
java.lang.Exception: Failed to create "java:comp/env/ejb/local/ActivityManagerLocalBean" bean; exception reported is: "javax.naming.NameNotFoundException: java:comp/env/ejb/local/ActivityManagerLocalBean not found in CubeEngineBean
at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:256)
<2010-04-06 09:56:36,904> <ERROR> <declaration.collaxa.cube.engine.dispatch> <BaseDispatchTask::run> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: Failed to create "java:comp/env/ejb/local/ActivityManagerLocalBean" bean; exception reported is: "javax.naming.NameNotFoundException: java:comp/env/ejb/local/ActivityManagerLocalBean not found in CubeEngineBean
at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:256)
at java.lang.Thread.run(Thread.java:595)
<2010-04-06 10:00:32,942> <ERROR> <declaration.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:109)
5 processes have been loaded for BPEL domain "Support".
<2010-04-06 09:56:36,897> <ERROR> <declaration.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
java.lang.Exception: Failed to create "java:comp/env/ejb/local/ActivityManagerLocalBean" bean; exception reported is: "javax.naming.NameNotFoundException: java:comp/env/ejb/local/ActivityManagerLocalBean not found in CubeEngineBean
at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:256)
<2010-04-06 09:56:36,904> <ERROR> <declaration.collaxa.cube.engine.dispatch> <BaseDispatchTask::run> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: Failed to create "java:comp/env/ejb/local/ActivityManagerLocalBean" bean; exception reported is: "javax.naming.NameNotFoundException: java:comp/env/ejb/local/ActivityManagerLocalBean not found in CubeEngineBean
at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:256)
at java.lang.Thread.run(Thread.java:595)
<2010-04-06 10:00:32,942> <ERROR> <declaration.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:109)
Solution:
Follow http://download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm
For proper configuration.
References:
http://download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm
No comments:
Post a Comment