[
https://jira.jboss.org/jira/browse/EJBTHREE-1969?page=com.atlassian.jira....
]
Shawn Kerstetter commented on EJBTHREE-1969:
--------------------------------------------
I ran into this issue when I toggled this setting in
deployers/ear-deployer-jboss-beans.xml
[code]
<bean name="EARClassLoaderDeployer"
class="org.jboss.deployment.EarClassLoaderDeployer">
<!-- A flag indicating if ear deployments should have their own scoped
class loader to isolate their classes from other deployments.
SEK NOTE: I tried to enable this in 5.1AS but ran into:
https://jira.jboss.org/jira/browse/EJBTHREE-1969
-->
<property name="isolated">false</property>
[/code]
EJB3 deployments lead to java.lang.IllegalStateException: Null
beannMetaData
-----------------------------------------------------------------------------
Key: EJBTHREE-1969
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1969
Project: EJB 3.0
Issue Type: Bug
Affects Versions: 1.1.22
Reporter: jaikiran pai
Assignee: jaikiran pai
Attachments: freeads.ear, Freeads.rar, helloWorld2Bad.ear, helloWorld2Good.ear
There has been more than one instance where users have reported issues around EJB3
deployments which leads to exception like this:
Caused by: java.lang.IllegalStateException: Null beannMetaData
at
org.jboss.ejb3.interceptors.metadata.BeanInterceptorMetaDataBridge.setupMetaDataLists(BeanInterceptorMetaDataBridge.java:315)
at
org.jboss.ejb3.interceptors.metadata.BeanInterceptorMetaDataBridge.initialise(BeanInterceptorMetaDataBridge.java:235)
at
org.jboss.ejb3.interceptors.metadata.BeanInterceptorMetaDataBridge.(BeanInterceptorMetaDataBridge.java:138)
at
org.jboss.ejb3.interceptors.metadata.AdditiveBeanInterceptorMetaDataBridge.(AdditiveBeanInterceptorMetaDataBridge.java:48)
at org.jboss.ejb3.aop.BeanContainer.initialize(BeanContainer.java:194)
at org.jboss.ejb3.EJBContainer.(EJBContainer.java:249)
One such forum thread discussion is referenced in this JIRA. The issue appears to be
around the way the deployment has been packaged. This needs more investigation and a fix
(or an explanation about why this happens and the correct way to package the culprit
application).
--
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