EJB errors on WAS 6.0 and 6.1

Every once in a while, it will be noted that there is an OBJECT_NOT_EXIST BAD_SERVER_ID in the nodeagent traces which could make the underlying EJBs on that node unavailable. Now this may affect just one JVM, on the node. YOU could have multiple JVMs on a single node.

Symptom : Client gets an XA Error in the prepare phase, the NodeAgent gets BAD_SERVER_ID and the EJB hosting JVM on the nodeagent's node gets a Timeout due to no client activity for 60 seconds.

Resolution : restart the JVM that is getting the timeout due to no client activity. A PMR has been opened with IBM to fix this issue.

Reason : ReactivateServers is a method where all the JVMs on a node are requested to register their EJBs. You could find that in the nodeagent ffdc logs there is a NO_PERMISSION related to this method.  This generally happens when a nodeagent is restarted and th underlying EJB hosting JVMs on that node are not restarted after that.

Async IO Errors With Http Requests for WAS 6.1

Async IO RC 76 Socket is already connected. This issue happens under load with http traffic. I will provide more info in my comments later.

Pinkal

WebSPhere issues with LTPA tokens

A new APAr was generated PK96506 , that deals with the CORBA.NO_PERMISSION when making remote ejb calls. Blog here for more details.