Fix (APAR):  JR25695

Status:  Fix

Release:  6.0.1.4,6.0.1.3

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  32103

Date: 2007-02-01

Abstract:  User will meet javax.naming. NameNotFoundException: Name comp/env/ jms not found in context "java:" in Webservice import binding over jms when upgrade from 6010, 6011 or 6012 to 60

Description/symptom of problem:  
JR25695 resolves the following problem:

ERROR DESCRIPTION:                                              
ESR: WPS 6.0.1.3 gives error message ExceptionUtil E            
CNTR0020E: EJB                                                  
threw an unexpected (non-declared) exception during invocation  
of                                                              
method "getResource" on bean "BeanId                            
(AA_BPELv6_MappingApp#AA_BPELv6_MappingEJB.jar#Module, null)".  
Exception data: javax.naming.NameNotFoundException: Name        
comp/env/jms                                                    
not found in context "java:".                                   
                                                                
WPS 6.0.1.3 on WAS ND 6.0.2.13 with a dmgr, a BPC cluster       
of 2                                                            
appservers where this app is deployed, an SIB Cluster with one  
messaging engine and 2 nodeagents all on one box.               
This used to work before the upgrade from WPS 6.0.1.1           
Atteched file is SystemOut.log from the appserver that showed   
the error.                                                      

LOCAL FIX:                                                      
                                                                

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users

PROBLEM DESCRIPTION:
User will meet javax.naming.
NameNotFoundException: Name comp/env/
jms not found in context "java:" in
Webservice import binding over jms
when upgrade from 6010, 6011 or 6012
to 6013 or 6014.

RECOMMENDATION:
None

The problem happens only for the SCA modules that include
Webservice import binding over jms and are installed before
upgrade. If user re-install the SCA module after upgrade,
there is no such problem.

The exception is like: java:comp/env/jms/MyQCF cannot be
resolved.: caused by: javax.naming.NameNotFoundException:
Name comp/env/jms not found in context "java:".

at com.ibm.ws.sca.internal.ejb.util.JndiAdapter.<init>
(JndiAdapter.java:47)

at com.ibm.ws.sca.internal.ejb.util.JndiAdapterFactory.
createAdapter(JndiAdapterFactory.java:39)

at org.eclipse.emf.common.notify.impl.AdapterFactoryImpl.
adaptNew(AdapterFactoryImpl.java:112)

at org.eclipse.emf.common.notify.impl.AdapterFactoryImpl.
adapt(AdapterFactoryImpl.java:98)

at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.
getResource(ModuleSessionBean.java:229)

at com.ibm.wsspi.sca.ejb.module.EJSLocalStatelessModule_
43132892.getResource(Unknown Source)

at com.ibm.ws.sca.internal.webservice.handler.PortHandler.
fixJmsEndpointJavaEnvPrefix(PortHandler.java:479)

at com.ibm.ws.sca.internal.webservice.handler.PortHandler.
<init>(PortHandler.java:422)

at com.ibm.ws.sca.internal.webservice.handler.WebService
ImportHandler.processMessage(WebServiceImportHandler.java:186)

at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.
processMessage(MessageDispatcherImpl.java:465)

PROBLEM CONCLUSION:                                             
The problem has been fixed by install the iFix.                 


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: