Fix (APAR): JR30465 Status: Fix Release: 6.0.1.6,6.0.1.5,6.0.1.4 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 77934 Date: 2008-10-28 Abstract: Service Component Architecture is writing large ffdc output. This is causing OutOfMemory issues. Description/symptom of problem: JR30465 resolves the following problem: ERROR DESCRIPTION:? OutOfMemory is thrown when SCA Logger writes large objects to FFDC. SystemOut logs of the server will indicate symptoms as: [9/10/08 14:56:43:223 GMT-05:30] 00000b0c ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "transactionNotSupportedActivitySessionNotSupported" on bean "BeanId(iesthrOutbound_pf_v1App#iesthrOutbound_pf_v1EJB.jar#Modu le, null)". Exception data: java.lang.OutOfMemoryError at java.io.StringWriter.write(StringWriter.java(Compiled Code)) at java.io.BufferedWriter.flushBuffer(BufferedWriter.java(Compiled Code)) at java.io.BufferedWriter.flush(BufferedWriter.java(Compiled Code)) at java.io.PrintWriter.flush(PrintWriter.java(Compiled Code)) at com.ibm.ws.sca.logging.ObjectDumper.dump(ObjectDumper.java(Inlin ed Compiled Code)) at com.ibm.ws.sca.logging.impl.JSR47LogImpl.ffdc(JSR47LogImpl.java( Inlined Compiled Code)) at com.ibm.ws.sca.internal.managed.WASLogImpl.ffdc(WASLogImpl.java( Compiled Code)) at com.ibm.ws.sca.internal.j2c.J2CInterfaceBindingImpl.invoke(J2CIn terfaceBindingImpl.java(Compiled Code)) at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.invokeDynam icImport(J2CImportHandler.java(Compiled Code)) at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.processMess age(J2CImportHandler.java(Compiled Code)) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proce ssMessage(MessageDispatcherImpl.java(Compiled Code)) at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process( ManagedMessageImpl.java(Compiled Code)) at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.processUOWMe ssage(ModuleSessionBean.java(Compiled Code)) at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.transactionN otSupportedActivitySessionNotSupported(ModuleSessionBean.java(In lined Compiled Code)) at com.ibm.wsspi.sca.ejb.module.EJSLocalStatelessModule_43132892.tr ansactionNotSupportedActivitySessionNotSupported(EJSLocalStatele ssModule_43132892.java(Compiled Code)) at com.ibm.ws.sca.internal.uow.handler.UOWStrategyImpl.transactionL ocalActivitySessionFalse(UOWStrategyImpl.java(Compiled Code)) LOCAL FIX:? N/A PROBLEM SUMMARY:? USERS AFFECTED: WebSphere Process Server 6.0.1.x users PROBLEM DESCRIPTION: Service Component Architecture is writing large ffdc output. This is causing OutOfMemory issues. RECOMMENDATION: None When an exception occurs with large business objects, such as context data, the server tries to output the context data to FFDC, which requests a large heap and causes an OutOfMemory error. java.lang.OutOfMemoryError at java.io.StringWriter.write(StringWriter.java(Compiled Code)) at java.io.BufferedWriter.flushBuffer(BufferedWriter.java (Compiled Code)) at java.io.BufferedWriter.flush(BufferedWriter.java (Compiled Code)) at java.io.PrintWriter.flush(PrintWriter.java(Compiled Code)) at com.ibm.ws.sca.logging.ObjectDumper.dump(ObjectDumper.java (Compiled Code)) at com.ibm.ws.sca.logging.impl.JSR47LogImpl.ffdc (JSR47LogImpl.java:221) at com.ibm.ws.sca.internal.managed.WASLogImpl.ffdc (WASLogImpl.java:44) at com.ibm.ws.sca.internal.j2c.J2CInterfaceBindingImpl.invoke (J2CInterfaceBindingImpl.java(Compiled Code)) at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler. invokeDynamicImport(J2CImportHandler.java(Compiled Code)) at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler. processMessage(J2CImportHandler.java:301) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl. processMessage(MessageDispatcherImpl.java(Compiled Code)) PROBLEM CONCLUSION:? This interim fix removes large context data from FFDC output. Applying this fix resolves the problem. 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: