Fix (APAR): JR30730 Status: Fix Release: 6.0.2.5,6.0.2.4,6.0.2.3 Operating System: AIX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 25732 Date: 2008-11-17 Abstract: A java.lang.ClassCastException occurs in com.ibm.j2ca.jdbc.JDBCInteraction. execute method when invoking an outbound operation involving a EIS binding of JDBCResourceAdapter. The e Description/symptom of problem: JR30730 resolves the following problem: ERROR DESCRIPTION:? java.lang.ClassCastException in com.ibm.j2ca.jdbc.JDBCInteractio n.execute method when invoking an outbound operation involving a EIS binding of JDBCResourceAdapter. LOCAL FIX:? a Fix is available PROBLEM SUMMARY:? USERS AFFECTED: WebSphere Process Server 6.0.2.x, 6.1.0.x, and 6.1.2.x users. PROBLEM DESCRIPTION: A java.lang.ClassCastException occurs in com.ibm.j2ca.jdbc.JDBCInteraction. execute method when invoking an outbound operation involving a EIS binding of JDBCResourceAdapter. The exception is caused intermittently in different operations and only happens during heavy load. Exception: [8/26/08 13:56:14:581 PDT] 00000064 Exc eptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception dur ing invocation of method "transactionNo tSupportedActivitySessionNotSupported" on bean "BeanId(MultiInputInventoryApp# MultiInputInventoryEJB.jar#Module, null )". Exception data: javax.resource.Reso urceException: java.lang.ClassCastExcep tion at com.ibm.j2ca.jdbc.JDBCInteraction.e xecute(JDBCInteraction.java(Compiled Co de)) at com.ibm.ws.sca.internal.j2c.J2CMeth odBindingImpl.invoke(J2CMethodBindingIm pl.java(Compiled Code)) at com.ibm.ws.sca.internal.j2c.J2CInte rfaceBindingImpl.invoke(J2CInterfaceBin dingImpl.java(Compiled Code)) at com.ibm.ws.sca.internal.j2c.handler .J2CImportHandler.invokeDynamicImport(J 2CImportHandler.java(Compiled Code)) at com.ibm.ws.sca.internal.j2c.handler .J2CImportHandler.processMessage(J2CImp ortHandler.java(Compiled Code)) at com.ibm.ws.sca.internal.message.imp l.MessageDispatcherImpl.processMessageW ithPCI(MessageDispatcherImpl.java(Compi led Code)) at com.ibm.ws.sca.internal.message.imp l.MessageDispatcherImpl.processMessage( MessageDispatcherImpl.java(Compiled Cod e)) at com.ibm.ws.sca.internal.message.imp l.ManagedMessageImpl.process(ManagedMes sageImpl.java(Compiled Code)) at com.ibm.wsspi.sca.ejb.module.impl.M oduleSessionBean.processUOWMessage(Modu leSessionBean.java(Compiled Code)) at com.ibm.wsspi.sca.ejb.module.impl.M oduleSessionBean.transactionNotSupporte dActivitySessionNotSupported(ModuleSess ionBean.java(Inlined Compiled Code)) at com.ibm.wsspi.sca.ejb.module.EJSLoc alStatelessModule_43132892.transactionN otSupportedActivitySessionNotSupported( EJSLocalStatelessModule_43132892.java(C ompiled Code)) at com.ibm.ws.sca.internal.uow.handler .UOWStrategyImpl.transactionLocalActivi tySessionFalse(UOWStrategyImpl.java(Com piled Code)) at com.ibm.ws.sca.internal.uow.handler .JoinUOWHandler.processMessage(JoinUOWH andler.java(Compiled Code)) at com.ibm.ws.sca.internal.message.imp l.MessageDispatcherImpl.processMessageW ithPCI(MessageDispatcherImpl.java(Compi led Code)) at com.ibm.ws.sca.internal.message.imp l.MessageDispatcherImpl.processMessage( MessageDispatcherImpl.java(Compiled Cod e)) at com.ibm.ws.sca.internal.proxy.impl. ProxyInvocationHandlerImpl.invoke(Proxy InvocationHandlerImpl.java(Compiled Cod e)) at $Proxy15.processMessage(Unknown Sou rce) at com.ibm.wsspi.sca.webservice.bean.i mpl.WebServiceBeanImpl.processInvoke(We bServiceBeanImpl.java(Compiled Code)) at com.ibm.wsspi.sca.webservice.ejb.im pl.WebServiceSessionBean.invokeWS(WebSe rviceSessionBean.java(Compiled Code)) at com.ibm.wsspi.sca.webservice.ejb.im pl.WebServiceSessionBean.invoke(WebServ iceSessionBean.java(Inlined Compiled Co de)) at sun.reflect.GeneratedMethodAccessor 92.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccesso rImpl.invoke(DelegatingMethodAccessorIm pl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Met hod.java(Compiled Code)) RECOMMENDATION: None This problem is caused by thread synchronization and some connection factory global variable settings. After setting up proper connection factory variables this problem has been resolved in high load environment. PROBLEM CONCLUSION:? This interim fix includes the solution for thread synchronization and connection factory global variable settings. Once customer applies this interim fix, they wont see this problem anymore. Directions to apply fix: Download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Process Server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server. Additional Information: