[
https://jira.jboss.org/jira/browse/JBAS-6290?page=com.atlassian.jira.plug...
]
Aul Kapoor closed JBAS-6290.
----------------------------
Resolution: Done
the EJB invocation was not failing because of the ServletContextListener but due to Remote
interface was there in both the EJB and Web Project. It worked fine with the earlier Jboss
releases but result in NullPointerException in Jboss 5.0.0 CR2.
There's need to throw appropraite excpetion with message if server can't handle
two Remote interface lying in web and app Project in same EAR..It worked fine with earlier
releases of Jboss.
EJB call fails from ServletContextListener
------------------------------------------
Key: JBAS-6290
URL:
https://jira.jboss.org/jira/browse/JBAS-6290
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.0.0.CR2
Reporter: Aul Kapoor
Assignee: Carlo de Wolf
Priority: Critical
Fix For: JBossAS-4.2.4.GA
Our application EAR has Web and App Module. The App Module has a stateless bean which
needs to be called from the ServletContextListener of the WebModule. The jndi lookups
return the EJBObject of the corresponding bean but when the method is invoked exception is
raised as follows.
Caused by: java.lang.NullPointerException
at
org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:420)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:97)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy192.invoke(Unknown Source)
at
org.jboss.ejb3.proxy.handler.session.SessionSpecProxyInvocationHandlerBase.invoke(SessionSpecProxyInvocationHandlerBase.java:125)
After the EAR is deployed the EJB call can be successfully made through any servlet but
fails if made from ServletContextListener
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira