[jboss-jira] [JBoss JIRA] Resolved: (JBAS-8126) CNFE Exceptions due to the wrong classloader being used
Alexey Loubyansky (JIRA)
jira-events at lists.jboss.org
Fri Jul 2 12:15:46 EDT 2010
[ https://jira.jboss.org/browse/JBAS-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Loubyansky resolved JBAS-8126.
-------------------------------------
Fix Version/s: 6.0.0.M4
Resolution: Done
The issue showed up when a stateful session (or EJB2 entity using global cache) is trying to lookup an EJB3 bean (look up of EJB2 didn't show the problem) in its ejbPassivate.
This is fixed now.
> CNFE Exceptions due to the wrong classloader being used
> -------------------------------------------------------
>
> Key: JBAS-8126
> URL: https://jira.jboss.org/browse/JBAS-8126
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-5.1.0.GA
> Reporter: Stelios Koussouris
> Assignee: Alexey Loubyansky
> Fix For: 6.0.0.M4
>
>
> The unified classloader is used loading an interface from another jar archive in the /deploy when that interface is called from within a scoped EAR rather than the interface included in the EAR itself.
> Our tests show when an interface is in a jar in the deploy directory and also in the scoped my.ear Once passivate gets called from a class within the EAR, that calls that interface, then it throws a ClassCastException on ClassLocal myEJB = ClassLocal.class.cast(obj);
> However it is actually a ClassNotFound, looking in the debugger. We see that instead of using the context of the ejb which would be the EAR classloader, the unified classloader is used instead and hence the resulting exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list