eFix (APAR): PQ65264
 
Status:      efix

Release: WebSphere 4.0.4

Operating System: All

Supersedes eFixes:  None 

CMVC defect: PQ65264 

Byte size of APAR: 1,057,536

Date: 8/21/2002

Title:	PQ63548

Abstract: WLM and Security enabled ORB client hangs on operation of read__com_ibm_ejs_sm_beans_SeriousEvent__com_ibm_ejs_sm_beans_SeriousEvent__long when adminServer was purposely brought down.

Description/symptom of problem: 

Thread stack dump from the hung client process

    "Thread-4" (TID:0x901508, sys_thread_t:0x22D40F58, state:CW, native ID:0x92C) prio=5
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:429)
	at com.ibm.rmi.util.Condition.wait(Condition.java:32)
	at com.ibm.CORBA.iiop.IIOPConnection.writeLock(IIOPConnection.java:1306)
	at com.ibm.CORBA.iiop.IIOPConnection.writeLock(IIOPConnection.java:1283)
	at com.ibm.CORBA.iiop.IIOPConnection.send(IIOPConnection.java:1495)
	at com.ibm.CORBA.iiop.IIOPConnection.locate(IIOPConnection.java:2011)
	at com.ibm.CORBA.iiop.GIOPImpl.locate(GIOPImpl.java:189)
	at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1155)
	at com.ibm.CORBA.iiop.ClientDelegate.non_existent(ClientDelegate.java:1687)
	at org.omg.CORBA.portable.ObjectImpl._non_existent(ObjectImpl.java:92)
	at com.ibm.ISecurityLocalObjectBaseL13Impl.VaultImpl.init_security_context(VaultImpl.java:2930)
	at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.establishSecurityContext(SecurityConnectionInterceptor.java:913)
	at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getSecureAssociation(SecurityConnectionInterceptor.java:2309)
	at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getConnectionKey(SecurityConnectionInterceptor.java:1579)
	at com.ibm.CORBA.iiop.ConnectionTable.get(ConnectionTable.java:334)
	at com.ibm.CORBA.iiop.GIOPImpl.createRequest(GIOPImpl.java:152)
	at com.ibm.CORBA.iiop.GIOPImpl.createRequest(GIOPImpl.java:133)
	at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1080)
	at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:1877)
	at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:245)
	at com.ibm.ejs.sm.beans._SeriousEventReader_Stub.read(_SeriousEventReader_Stub.java:234)
	at com.ibm.websphere.advance.tivoli.SeriousEventEngine.run(SeriousEventEngine.java:596)
	at java.lang.Thread.run(Thread.java:512)

ORB trace shows client ORB hangs on the following entry and it is being the last entry as well during operation of read__com_ibm_ejs_sm_beans_SeriousEvent__com_ibm_ejs_sm_beans_SeriousEvent__long or other similar System Managment operation(s). 

[8/5/02 15:34:54:316 EDT] 68d09ac8 ORBRas        > com.ibm.CORBA.iiop.ClientRequestImpl ijavaorb P=88428:O=0:CT Entry
                                 invoke(isOneway=false)




Directions to apply efix:

1) Create temporary "efix" directory to store the jar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

5) Restart WebSphere

6) The temp directory may be removed but the jar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<efix> directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/<efix#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_efix#>

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the 
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite 
prompts.



Additional Information:

------------------------------------------------------------------