Exceptions and incorrect processing behavior can be seen if transactions are being processed prior to the local server is ready for e-business. Messages are sent to remote servers in the cluster for processing, which can lead to exceptions or incorrect transaction processing.
When a server is starting, sometimes an application might start before the server is ready and open for e-business. In a clustered environment, the Message Driven Bean (MDB) might have messages in its queue. If the local server is not open for e-business and is still starting, the message off the queue is sent remotely to another server in the cluster. This scenario might lead to unexpected results if remote servers are processing the transaction and send it back to the local node after processing.
You might see the following exceptions, which is not a complete list:
Resolving the problem
Enable the following Java virtual machine (JVM) property:
com.ibm.ejs.j2c.J2CServerListener.deferEndpointActivation = true
This property should not have any risk or drawbacks. However, it is a good practice to use it in a test environment before implementing it in production.