Fix (APAR):  PK53192

Status:  Fix

Release:  6.1.0.9,6.1.0.7,6.1.0.11

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

Supersedes Fixes:  

CMVC Defect:  460971

Byte size of APAR:  15600

Date: 2007-10-11

Abstract:  CWSIT0103E exception from TrmSICoreConnectionFactoryImpl .localBootstrap(), with a standalone application server. This issue is unlikely to affect JMS applications connecting to a 

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

ERROR DESCRIPTION:                                              
CWSIT0103E from TrmSICoreConnectionFactoryImpl.localBootstrap   
Exception stack is as follows:                                  
 at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.   
   localBootstrap(TrmSICoreConnectionFactoryImpl.java:351)      
 at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.   
   createConnection(TrmSICoreConnectionFactoryImpl.java:292)    
 at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.   
   createConnection(TrmSICoreConnectionFactoryImpl.java:210)    

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
Users of the default messaging provider
for WebSphere Application Server V6.1

PROBLEM DESCRIPTION:
CWSIT0103E exception from
TrmSICoreConnectionFactoryImpl
.localBootstrap(), with a standalone
application server.
This issue is unlikely to affect
JMS applications connecting to a
service integration bus.
Instead, this issue affects other
IBM products using the service
integration bus as a component.

RECOMMENDATION:
None

In a standalone environment, the service integration bus does
not advertise the location of all destinations to the workload
management component of WebSphere Application Server.
However, the TrmSICoreConnectionFactoryImpl.localBootstrap()
code was querying the workload management component for
destination information, and failing with the following stack:
.
CWSIT0103E
at com.ibm.ws.sib.trm.client.
TrmSICoreConnectionFactoryImpl.localBootstrap()
at com.ibm.ws.sib.trm.client.
TrmSICoreConnectionFactoryImpl.createConnection()
at com.ibm.ws.sib.trm.client.
TrmSICoreConnectionFactoryImpl.createConnection()

PROBLEM CONCLUSION:                                             
This APAR fixes the problem.                                    
The service integration bus no long queries the workload        
management component for destination information in a           
standalone environment.                                         


Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release 6.0
x_ Application Server (Express or BASE)
x_ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

Install Fix to:
Method:
x_ Application Server Nodes
__ Deployment Manager Nodes
__ 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 PKxxxxx.pak file directly to the maintenance directory

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 (PKxxxxx.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 (PKxxxxx.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: