Fix (APAR):  JR31081

Status:  Fix

Release:  6.1.2.1,6.1.2,6.1.0.2,6.1.0.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  156817

Date: 2009-02-19

Abstract:  While WebSphere Process Server is starting, and the monitor component has not been initialized yet, other components may invoke the monitor component to fire Common Base Events (CB

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

ERROR DESCRIPTION:?                                             
Customer received below exception when starting a WPS 6.1       
cluster with correct configuration:                             
CEMEM0003E: The specified emitter factory was not found in JNDI.
javax.naming.NameNotFoundException: Context:                    
DEVCELL1/clusters/DEVXCS.AppTarget, name:                       
com/ibm/events/configuration/emitter/Default: First component in
name configuration/emitter/Default not found.                   

LOCAL FIX:?                                                     
N/A                                                             

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server 6.1.0.x and
6.1.2.x users who emit Common Base Events
when the server is in starting status.

PROBLEM DESCRIPTION:
While WebSphere Process Server is
starting, and the monitor
component has not been initialized
yet, other components may invoke the
monitor component to fire Common
Base Events (CBE). In
these cases, the Common Event
Infrastructure's (CEI) emitter factory
will be initialized incorrectly,
and CBEs wont be fired. The
exception will be logged in the
First Failure Data Capture (FFDC)
file and the SystemOut.log.

RECOMMENDATION:
None

In some rare cases, users can not fire Common Base Events,
even after WebSphere Process Server is started.

PROBLEM CONCLUSION:?                                            
Applying the interim fix will resolve the issue.                


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: