Windoz XP
java version "1.4.2_04"
Issue 1:
When the EAR which has an inbound connector gets
undeployed, the container associated with the
MessageEndpointFactory is set to NULL before
afterDelivery() or release() gets called on the endpoint
proxy, so when afterDelivery() or release() gets called,
the MessageEndpointInterceptor is throwing
NULLPointerException on
tm = container.getTransactionManager();
in function endTransaction().
Fix:
Check if container is NULL, if it is NULL, use
this.transaction to do the proper transaction operation.
See attached file for fixes we used(endTransaction
method).
Issue 2:
We're getting a NP from the Work thread that is ending.
Looks like from the server.log the classloader is
unregistered before the Work thread completes.
java.lang.NullPointerException
at org.jboss.mx.loading.LoadMgr3.beginLoadTask
(LoadMgr3.java:129)
Stopping the server doesn't produce this error. Is this a
race condition? It this a separate bug to be logged, a
grey area?
org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor
Logged In: YES
user_id=9459
You shouldn't even be in the MessageEndpoint at this point.
You are supposed to respond the endpointDeactivation by stopping
all work and/or waiting for inflight work to complete.
You don't return from endpointDeactivation until you have
done that.