Fix (APAR):  JR31260

Status:  Fix

Release:  6.0.2.5,6.0.2.4

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  15398

Date: 2009-01-07

Abstract:  A newly installed application fails to start with a CWSTM0008E message logged in the SystemOut.log.

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

ERROR DESCRIPTION:?                                             
Selector table updated failed when start a new installed        
application with a selector                                     
                                                                
When the application invokes the selector, you may see the      
following exception:                                            
                                                                
**********                                                      
com.ibm.wbiservers.selector.scdl.selectorimpl.handler.SelectorHa
ndler processMessage CWLFW0003E: An error occurred while        
processing a selector component.  See the logged exception.     
                                                                
com.ibm.wbiserver.common.exception.SelectorException: An        
OperationSelectionTable for the operation, operation1 does not  
exist.                                                          
 at                                                             
com.ibm.wbiservers.common.selection.GenericSelector.selectTarget
s(GenericSelector.java:80)                                      
**********                                                      

LOCAL FIX:?                                                     
No Local Fix                                                    

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server 6.0.2.x users

PROBLEM DESCRIPTION:
A newly installed application fails to
start with a CWSTM0008E message logged
in the SystemOut.log.

RECOMMENDATION:
None

The business rule and selector components have code that runs
during application startup that tries to process all files in
the application that have a .component file extension.  The
assumption is that all of these files represent Service
Component Architecture components.  Sometimes, however,
applications built using WebSphere Integration Developer will
contain a .component file that does not represent an Service
Component Architecture component.  The business rule and
selector code tries to process the file anyway.  This causes an
error when the file can't be parsed as an Service Component
Architecture component file.  An error message with message ID
CWSTM0008E is logged to the SystemOut.log file from the
CustomizationComponentImpl class.  This is normally
accompanied by an exception that indicates some sort of file
parsing problem.  The application fails to start which can
then cause other problems later on since the application is
unavailable.

PROBLEM CONCLUSION:?                                            
The business rule and selector code was changed to ignore       
the extraneous .component files in the application.  This fix   
is targeted for inclusion in fixpack 6.0.2.6.  It is already    
available in release 6.1.0.x and 6.2.0.x.                       


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: