Hey all,
I'm uncertain whether this is a bug or whether it's the result of doing things
that shouldn't be done, but we're triggering a NPE in the
StatelessInstanceManager during startup:
java.lang.NullPointerException: Cannot invoke
"org.apache.openejb.core.stateless.StatelessInstanceManager$Data.poolPop()"
because "data" is null
at
org.apache.openejb.core.stateless.StatelessInstanceManager.getInstance(StatelessInstanceManager.java:218)
at
org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:204)
at
org.apache.openejb.core.ivm.EjbObjectProxyHandler.synchronizedBusinessMethod(EjbObjectProxyHandler.java:252)
at
org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:247)
at
org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:89)
at
org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:345)
at jdk.proxy11/jdk.proxy11.$Proxy257.export(Unknown Source)
The proxy object is a stateless EJB injected into an MDB. If TomEE is stopped
with unprocessed messages on our topic, a trail of NPEs is created until the
stateless bean is successfully injected.
Our TomEE version is 10.2.0
--
Thomas Butz
OPTITOOL GmbH
