Fix (APAR):  PK58313

Status:  Fix

Release:  6.1.0.13

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

Supersedes Fixes:  

CMVC Defect:  478937

Byte size of APAR:  22494

Date: 2008-06-18

Abstract:  CEI is not working properly (the JMS part is not functioning) on a cluster based on a server with CEI if security is on.

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

ERROR DESCRIPTION:                                              
After promoting standalone server to cluster, configuring       
datasources and HA policies, then start cluster, in cluster's   
every server log shows that                                     
[10/29/07 9:37:23:953 GMT-08:00] 0000007b ActivationSpe E       
J2CA0155W: The lookup of the Authentication Alias               
CommonEventInfrastructureJMSAuthAlias, assigned to the          
ActivationSpec jms/cei/QueueActivationSpec                      
(com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl) by     
application EventService#EventServerMdb.jar#EventBusMdbBean     
has failed.                                                     

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
Users of Common Event Infrastructure (CEI)
on IBM WebSphere Application Server V6.1

PROBLEM DESCRIPTION:
CEI is not working properly (the JMS
part is not functioning) on a cluster
based on a server with CEI if security
is on.

RECOMMENDATION:
None

The problem appears on a WebSphere Application Server Network
Deployment environment when security is on and a cluster is
created based on a serverwith CEI deployed on it. When the
cluster is created JMS resources are promoted to cluster scope.
During this action the JMSAuthAlias set at the JMS resource
level is removed, preventing CEI from working properly in
the cluster.

PROBLEM CONCLUSION:                                             
This fix will preserve the JMSAuthAlias at cluster scope level. 
The fix for this APAR is currently targeted for inclusion in    
fix pack 6.1.0.15. Please refer to the Recommended Updates page 
for delivery information:                                       
                                                                
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  Fix applies to Editions:
Release 6.1 Network Deployment (ND)

Install Fix to:
Method:
_x_ Application Server Nodes
_x_ Deployment Manager Nodes
_x_ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy PK58313.pak file directly to the maintenance directory of the Update Installer

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PK58313.pak file which was copied in the maintenance directory).

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER 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, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PK58313.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.





Additional Information: