[jboss-jira] [JBoss JIRA] Commented: (JBAS-7588) Investigate org.jboss.test.ejb.lifecycle.test failures
Adrian Brock (JIRA)
jira-events at lists.jboss.org
Fri Jan 29 11:25:19 EST 2010
[ https://jira.jboss.org/jira/browse/JBAS-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12509300#action_12509300 ]
Adrian Brock commented on JBAS-7588:
------------------------------------
The issue here is that org.jboss.system.RMIClassLoader is no longer getting used.
So when it marshalls the proxy it is creating a new one against the wrong classloader.
/*
* Ignore the JVM, use the thread context classloader for proxy caching
*/
public Class<?> loadProxyClass(String codebase, String[] interfaces, ClassLoader ignored)
throws MalformedURLException, ClassNotFoundException
{
return delegate.loadProxyClass(codebase, interfaces, Thread.currentThread().getContextClassLoader());
}
It was previously configured in conf/jboss-service.xml before any subsystem (e.g. naming) used RMI.
If you don't do it that way it won't work.
There's actually no need to set this system property in this complicated manner anymore (its legacy config from when JDK1.3 didn't have
this feature), so I'd suggest the fix is:
1) Set the system property to our implementation in org.jboss.Main (if it is not already set)
2) Remove the mbean from deploy/legacy-jboss-service.xml
> Investigate org.jboss.test.ejb.lifecycle.test failures
> ------------------------------------------------------
>
> Key: JBAS-7588
> URL: https://jira.jboss.org/jira/browse/JBAS-7588
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: jaikiran pai
> Assignee: jaikiran pai
>
--
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
More information about the jboss-jira
mailing list