WPS – SCA trace causes the SCA module NullPointerException

Noticed that transaction rollback in the SystemOut.log, like:

[11/29/10 21:42:53:499 EST] 0000006a Recovery      I com.ibm.wbiserver.
management.FailedEventManagerMBean resubmitFailedEvents(List)
CWRCV0033I: The following number of failed events was resubmitted
successfully: "1".
[11/29/10 21:42:54:426 EST] 00000036 MA_IBISSTARSD I   begin
createOutb_Bpi_Msg_Stars: msg_id=1400010275, orderid=2010-11-29 16:48:
56.455674
[11/29/10 21:42:55:699 EST] 00000036 ESWorkBean    E com.ibm.wbiserver.
sequencing.work.ESWorkBean processMessageInBifurcatedSession
CWRES0016E: The message with msgId=8FD53ADC8A049ECB_6000087 and the
transaction will be rolled back. The exception is Fail to invoke [sca.
component.java.impl.Component1Impl3.public void sca.component.java.impl.
Component1Impl3.createOutb_Bpi_Msg_Stars(commonj.sdo.DataObject)] for
component [{MA_IBISSTARSDb}StarsBGtoBO].
[11/29/10 21:42:56:331 EST] 00000036 LocalExceptio E   CNTR0020E: EJB
threw an unexpected (non-declared) exception during invocation of
method "processMessageInBifurcatedSession" on bean "BeanId
(persistentLkMgr#persistentLkMgrEJB.jar#ESWork, null)". Exception data:
com.ibm.wbiserver.sequencing.exceptions.SequencingRuntimeException:
CWRES0015E: The message with msgId=8FD53ADC8A049ECB_6000087 failed
during processing. The error is Fail to invoke [sca.component.java.impl.
Component1Impl3.public void sca.component.java.impl.Component1Impl3.
createOutb_Bpi_Msg_Stars(commonj.sdo.DataObject)] for component
[{MA_IBISSTARSDb}StarsBGtoBO].
        at com.ibm.wbiserver.sequencing.work.ESWorkBean.processMessage
(ESWorkBean.java:177)
        at com.ibm.wbiserver.sequencing.work.ESWorkBean.
processMessageInBifurcatedSession(ESWorkBean.java:101)
        at com.ibm.wbiserver.sequencing.work.
EJSLocalStatelessESWork_ddc8f6c2.processMessageInBifurcatedSession
(Unknown Source)
        at com.ibm.wbiserver.sequencing.work.EsWorkImpl.run(EsWorkImpl.
java:235)
        at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.
java:268)
        at java.security.AccessController.doPrivileged(AccessController.
java:224)
        at javax.security.auth.Subject.doAs(Subject.java:495)
        at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.
java:131)
        at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.
java:89)
        at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.
java:335)
        at java.security.AccessController.doPrivileged(AccessController.
java:251)
        at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:777)
        at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go
(WorkWithExecutionContextImpl.java:222)
        at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.
java:159)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
Caused by: com.ibm.websphere.sca.ServiceRuntimeException: Fail to
invoke [sca.component.java.impl.Component1Impl3.public void sca.
component.java.impl.Component1Impl3.createOutb_Bpi_Msg_Stars(commonj.
sdo.DataObject)] for component [{MA_IBISSTARSDb}StarsBGtoBO]: caused
by: java.lang.NullPointerException
        at com.ibm.ws.sca.internal.java.handler.
JavaImplementationHandler.invokeSync(JavaImplementationHandler.java:473)
        at com.ibm.ws.sca.internal.java.handler.
JavaImplementationHandler.processMessage(JavaImplementationHandler.java:
306) 

The transactions kept failling. 

The root cause is the trace "SCA.*=all" caused this problem. After disabling the trace "SCA.*=all",
the transactions were going well. 

IBM provided an ifix to solve this issue JR37651 to solve this issue.
Advertisements

About this entry