Fix (APAR):  JR25492

Status:  Fix

Release:  6.0.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  35411

Date: 2006-12-14

Abstract:  The SCA container is failing to start because of a ConcurrentModification Exception.

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

ERROR DESCRIPTION:                                              
While restarting the server, the server has hung error is       
recieved                                                        
at the                                                          
                                                                
ADMU3200I: Server launched. Waiting for initialization status.  
                                                                
Message. On checking the SystemOut.log I keep seeing            
                                                                
[30/11/06 13:18:01:375 GMT] 0000000d ThreadMonitor W            
WSVR0605W: Thread "server.startup : 1" (00000031) has been      
active for 703781 milliseconds and may be hung.  There is/are 1 
thread(s) in total in the server that may be hung.              
[30/11/06 13:18:01:391 GMT] 0000000d ThreadMonitor W            
WSVR0605W: Thread "server.startup : 0" (00000030) has been      
active for 701594 milliseconds and may be hung.  There is/are 2 
thread(s) in total in the server that may be hung.              
[30/11/06 13:18:01:391 GMT] 0000000d ThreadMonitor W            
WSVR0605W: Thread "server.startup : 2" (00000032) has been      
active for 703828 milliseconds and may be hung.  There is/are 3 
thread(s) in total in the server that may be hung.              
[30/11/06 13:18:01:453 GMT] 0000000d ThreadMonitor W            
WSVR0605W: Thread "server.startup : 8" (00000036) has bee       
                                                                
It doesnt appear to be any pattern in the failure,sometimes     
it happens on the 3rd suite,sometimes the 10th, and sometimes   
not at all                                                      

LOCAL FIX:                                                      
None.                                                           

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users.

PROBLEM DESCRIPTION:
The SCA container is failing to start
because of a ConcurrentModification
Exception.

RECOMMENDATION:
None

The SCA container is failing to start because of a
ConcurrentModificationException. SCA detects this failure and
attempts to dump a large amount of information about the
environment at the time of the failure which is leading to
deadlock, and the user can not tell what the original failure
was and they are now deadlocked.

PROBLEM CONCLUSION:                                             
This IFIX fixes both problems.                                  


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: