Fix (APAR): JR27669 Status: Fix Release: 6.0.2.2 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 5855 Date: 2007-11-14 Abstract: If synchronized call between service modules fails with ServiceUnavailableException because callee module is not started, it would still fail with the same exception after callee m Description/symptom of problem: JR27669 resolves the following problem: ERROR DESCRIPTION: if applicationA makes a synchronous call to applicationB and applicationB is down, the call will fail as expected. however,when applicaitonB comes back online, the calls from A to B continue to fail. this has forced us to be very careful about how we start/stop STACKTRACE: mpl.WorkQueueManager.attemptIO(WorkQueueManager.java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueue Manager.java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueu eManager.java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code)) Caused by: com.ibm.bpe.api.RuntimeFaultException: CWWBE0003E: An error occurred during the invocation of the activity implementation 'Invoke'. at com.ibm.bpe.engine.BpelActivityKindInvoke.doActivate(BpelActivit yKindInvoke.java:904) at com.ibm.bpe.engine.BpelActivityStateInactive.activateOrSkip(Bpel ActivityStateInactive.java:222) at com.ibm.bpe.engine.BpelEngineCore.continueControlLink(BpelEngine Core.java:193) at com.ibm.bpe.engine.BpelContinueLinkMessage3.execute(BpelContinue LinkMessage3.java:86) at com.ibm.bpe.engine.BpelEngine.processInternalMessages(BpelEngine .java:5150) at com.ibm.bpe.framework.EngineMessageExecutionWorkObject.processAl lEngineMessages(EngineMessageExecutionWorkObject.java:254) at com.ibm.bpe.framework.EngineMessageExecutionWorkObject.run(Engin eMessageExecutionWorkObject.java:149) at com.ibm.bpe.framework.EngineMessageExecutor.execute(EngineMessag eExecutor.java:158) at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:691) at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:620) at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:570) at com.ibm.bpe.framework.sca.ProcessSessionBean.invokeEngineSync(Pr ocessSessionBean.java:933) at com.ibm.bpe.framework.sca.ProcessSessionBean.invokeEngineSync(Pr ocessSessionBean.java:905) at com.ibm.bpe.framework.sca.ProcessSessionBean.processMessage(Proc essSessionBean.java:261) ... 38 more Caused by: com.ibm.websphere.sca.ServiceUnavailableException: javax.naming.NameNotFoundException: Context: widCell/nodes/widNode/servers/server1, name: cell/persistent/sca/TestModuleB/export/ComponentBExport: First component in name TestModuleB/export/ComponentBExport not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]: caused by: javax.naming.NameNotFoundException: Context: widCell/nodes/widNode/servers/server1, name: cell/persistent/sca/TestModuleB/export/ComponentBExport: First component in name TestModuleB/export/ComponentBExport not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0] at com.ibm.ws.sca.internal.ejb.util.EJBStubAdapter.getStub(EJBStubA dapter.java:86) at com.ibm.ws.sca.internal.ejb.util.EJBStubHelper.lookup(EJBStubHel per.java:89) at com.ibm.ws.sca.internal.ejb.util.EJBStubHelper.lookup(EJBStubHel per.java:82) at com.ibm.ws.sca.internal.binding.handler.SCAImportBindingHandler. getExportEJBStub(SCAImportBindingHandler.java:141) at com.ibm.ws.sca.internal.binding.handler.SCAImportBindingHandler. processMessage(SCAImportBindingHandler.java:217) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proce ssMessageWithPCI(MessageDispatcherImpl.java:711) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proce ssMessage(MessageDispatcherImpl.java:1148) at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process( ManagedMessageImpl.java:587) at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.processUOWMe ssage(ModuleSessionBean.java:336) at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.transactionN otSupportedActivitySessionNotSupported(ModuleSessionBean.java:28 5) at com.ibm.wsspi.sca.ejb.module.EJSLocalStatelessModule_43132892.tr ansactionNotSupportedActivitySessionNotSupported(EJSLocalStatele ssModule_43132892.java:131) at com.ibm.ws.sca.internal.uow.handler.UOWStrategyImpl.transactionL ocalActivitySessionFalse(UOWStrategyImpl.java:381) at com.ibm.ws.sca.internal.uow.handler.JoinUOWHandler.processMessag e(JoinUOWHandler.java:126) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proce ssMessageWithPCI(MessageDispatcherImpl.java:711) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proce ssMessage(MessageDispatcherImpl.java:1148) at com.ibm.ws.sca.internal.proxy.impl.ProxyInvocationHandlerImpl.in voke(ProxyInvocationHandlerImpl.java:766) at $Proxy12.processMessage(Unknown Source) at com.ibm.bpe.invocation.SCAInvocationHandler.doinvoke_Sync_ReqRsp (SCAInvocationHandler.java:502) at com.ibm.bpe.invocation.SCAInvocationHandler.doinvoke(SCAInvocati onHandler.java:411) at com.ibm.bpe.invocation.SCAInvocationHandler.invoke(SCAInvocation Handler.java:205) at com.ibm.bpe.engine.BpelActivityKindInvoke.doActivate(BpelActivit yKindInvoke.java:461) ... 51 more Caused by: javax.naming.NameNotFoundException: Context: widCell/nodes/widNode/servers/server1, name: cell/persistent/sca/TestModuleB/export/ComponentBExport: First component in name TestModuleB/export/ComponentBExport not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0] at com.ibm.ws.naming.jndicos.CNContextImpl.processNotFoundException (CNContextImpl.java:4392) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1752) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1707) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl. java:1412) at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.jav a:1290) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:145) at javax.naming.InitialContext.lookup(InitialContext.java:361) at com.ibm.ws.sca.internal.ejb.util.EJBLocator$JndiLocator.locate(E JBLocator.java:461) at com.ibm.ws.sca.internal.ejb.util.EJBLocator.locate(EJBLocator.ja va:439) at com.ibm.ws.sca.internal.ejb.util.EJBObjectFactory.createStub(EJB ObjectFactory.java:72) at com.ibm.ws.sca.internal.ejb.util.EJBStubAdapter.getStub(EJBStubA dapter.java:84) ... 71 more LOCAL FIX: A workaround is that restart caller application after the error occured and callee is started. PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2 users and above. users who use synchronized call between service modules while callee module might start after caller module PROBLEM DESCRIPTION: If synchronized call between service modules fails with ServiceUnavailableException because callee module is not started, it would still fail with the same exception after callee module is started. RECOMMENDATION: None The code cached the exception thrown during the first call of caller before callee started and always returned it after callee started successfully. PROBLEM CONCLUSION: Remove the cache of exception. And the problem resolved after applying the fix. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system. Also 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 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. 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 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: