[jira] Updated: (GERONIMO-3233) Local EJB references cannot be resolved when inverse-classloading is set in web application
[
https://issues.apache.org/jira/browse/GERONIMO-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aman Nanner updated GERONIMO-3233:
--
Affects Version/s: (was: 2.0-M6)
2.1
2.0.x
Local EJB references cannot be resolved when inverse-classloading is set in
web application
-
Key: GERONIMO-3233
URL: https://issues.apache.org/jira/browse/GERONIMO-3233
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0.x, 2.1
Environment: Windows XP SP2
Reporter: Aman Nanner
Priority: Critical
Attachments: ejb-reference-fails.ear.zip
It seems that setting the {{inverse-classloading}} element in the
geronimo-web.xml for a web application causes Local EJB references to fail
when looked up. This is because a new SystemInstance is created via a
different classloader, and the existing SystemInstance singleton is not used.
Here is a stack trace of the error:
{code}
15:46:49,877 WARN [EjbFactory] Unable to lookup up EJB by reference name
'ejb/common/SequenceGenerator'; you must define the EJB reference
javax.naming.NamingException: Could not look up :
ejb/common/SequenceGenerator [Root exception is
java.lang.NullPointerException]
at org.apache.xbean.naming.context.ContextUtil.resolve(
ContextUtil.java:65)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:112)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:611)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:152)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:611)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:152)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:597)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
.
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:109)
at org.apache.catalina.valves.AccessLogValve.invoke(
AccessLogValve.java:563)
at org.apache.catalina.connector.CoyoteAdapter.service(
CoyoteAdapter.java:261)
at org.apache.coyote.http11.Http11Processor.process(
Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:581)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(
JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at org.apache.openejb.core.ivm.naming.IntraVmJndiReference.getObject(
IntraVmJndiReference.java:38)
at org.apache.openejb.core.ivm.naming.Reference.getContent(
Reference.java:40)
at org.apache.xbean.naming.context.ContextUtil.resolve(
ContextUtil.java:61)
... 50 more
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3233) Local EJB references cannot be resolved when inverse-classloading is set in web application
[
https://issues.apache.org/jira/browse/GERONIMO-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aman Nanner updated GERONIMO-3233:
--
Attachment: ejb-reference-fails.ear.zip
Here is a sample EAR file that can be deployed on Geronimo that demonstrates
the problem. Access the index.jsp to reproduce the issue.
Local EJB references cannot be resolved when inverse-classloading is set in
web application
-
Key: GERONIMO-3233
URL: https://issues.apache.org/jira/browse/GERONIMO-3233
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M6
Environment: Windows XP SP2
Reporter: Aman Nanner
Priority: Critical
Attachments: ejb-reference-fails.ear.zip
It seems that setting the {{inverse-classloading}} element in the
geronimo-web.xml for a web application causes Local EJB references to fail
when looked up. This is because a new SystemInstance is created via a
different classloader, and the existing SystemInstance singleton is not used.
Here is a stack trace of the error:
{code}
15:46:49,877 WARN [EjbFactory] Unable to lookup up EJB by reference name
'ejb/common/SequenceGenerator'; you must define the EJB reference
javax.naming.NamingException: Could not look up :
ejb/common/SequenceGenerator [Root exception is
java.lang.NullPointerException]
at org.apache.xbean.naming.context.ContextUtil.resolve(
ContextUtil.java:65)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:112)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:611)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:152)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:611)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:152)
at org.apache.xbean.naming.context.AbstractContext.lookup(
AbstractContext.java:597)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
.
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:109)
at org.apache.catalina.valves.AccessLogValve.invoke(
AccessLogValve.java:563)
at org.apache.catalina.connector.CoyoteAdapter.service(
CoyoteAdapter.java:261)
at org.apache.coyote.http11.Http11Processor.process(
Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:581)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(
JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at org.apache.openejb.core.ivm.naming.IntraVmJndiReference.getObject(
IntraVmJndiReference.java:38)
at org.apache.openejb.core.ivm.naming.Reference.getContent(
Reference.java:40)
at org.apache.xbean.naming.context.ContextUtil.resolve(
ContextUtil.java:61)
... 50 more
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
