Fix (APAR):  JR27169

Status:  Fix

Release:  6.0.2.2,6.0.2.1

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

Supersedes Fixes:  

CMVC Defect:  JR27169

Byte size of APAR:  13373

Date: 2007-08-23

Abstract:  In BPC Explorer, When a new instance is started.  The following exception is encountered - java.lang.NoClassDefFoundError: com/ibm /ws/sca/internal/message/impl/MessageDi spatcherI

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

ERROR DESCRIPTION:                                              
This problem:                                                   
                                                                
    Caused by: java.lang.NoClassDefFoundError:                  
com/ibm/ws/sca/internal/                                        
    message/impl/MessageDispatcherImpl                          
        at                                                      
com.ibm.ws.sca.internal.proxy.impl.ProxyInvocationHandlerImp    
    l.<init>(ProxyInvocationHandlerImpl.java:465)               
        at                                                      
com.ibm.wsspi.sca.webservice.bean.impl.WebServiceBeanImpl.pr    
    ocessInvoke(WebServiceBeanImpl.java:249)                    
        ... 41 more                                             
                                                                
...is likely caused by this earlier problem:                    
                                                                
    Caused by: java.util.ConcurrentModificationException        
        at                                                      
org.eclipse.emf.common.util.BasicEList$EIterator.checkModCou    
    nt(BasicEList.java(Inlined Compiled Code))                  
        at                                                      
org.eclipse.emf.common.util.BasicEList$EIterator.next(BasicE    
    List.java(Compiled Code))                                   
        at                                                      
com.ibm.ws.sca.internal.scdl.extensions.impl.ManagedExtensio    
                                                                
nPointImpl.getExtensions(ManagedExtensionPointImpl.java(Compiled
Co                                                              
    de))                                                        
        at                                                      
com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.g    
    etExtensions(MessageDispatcherImpl.java:971)                
        at                                                      
com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.<    
    clinit>(MessageDispatcherImpl.java:858)                     
        ... 22 more                                             
                                                                
When an exception is thrown through the static initializer      
(<clinit>)                                                      
of a class, the JVM marks the class as bad.  All subsequent     
requests to                                                     
load that class will result in the JVM throwing a               
NoClassDefFoundError.                                           

LOCAL FIX:                                                      
NONE.                                                           

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.x users and
Websphere Enterprise Server Bus 6.0.2.x
users.

PROBLEM DESCRIPTION:
In BPC Explorer, When a new instance is
started.  The following exception is
encountered -
java.lang.NoClassDefFoundError: com/ibm
/ws/sca/internal/message/impl/MessageDi
spatcherImpl



RECOMMENDATION:
None

SCA runtime fails to load the class (MessageDispatcherImpl)
sometimes when at start-up the code in the static block of the
class gets a Runtime exception
(ConcurrentModificationException) leads to class not been
loaded by JVM.
This in turn leads to NoClassDefFoundError by BPC or other
runtime components trying to use MessageDispatcherImpl class.

PROBLEM CONCLUSION:                                             
Applying iFix resolves this issue.                              


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.2.1 or 6.0.2.2 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 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 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) 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: