[jboss-jira] [JBoss JIRA] Commented: (JBAS-6600) Setting isolated=true on EarClassLoaderDeployer does not work
Adrian Brock (JIRA)
jira-events at lists.jboss.org
Tue Apr 14 07:54:36 EDT 2009
[ https://jira.jboss.org/jira/browse/JBAS-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462014#action_12462014 ]
Adrian Brock commented on JBAS-6600:
------------------------------------
This problem is caused by the domain name created by the EARClassLoaderDeployer not being
in canonical form for an ObjectName (i.e. properties in alphanumeric order).
The ear creates a domain with properties "service, url, extension"
2009-04-14 13:19:58,871 DEBUG [org.jboss.classloader.spi.ClassLoaderSystem] (RMI TCP Connection(2)-127.0.0.1) DefaultClassLoaderSystem at 113981b registered domain=ClassL
oaderDomain at 1689243{name=jboss.j2ee:service=EARDeployment,url='testscopedrar-nojbossapp.ear',extension=LoaderRepository parentPolicy=AFTER_BUT_JAVA_BEFORE parent=Class
LoaderDomain at 1672bbb{DefaultDomain}}
While the -ds.xml uses a domain that is in canonical form "extension, service. url"
2009-04-14 13:19:59,060 DEBUG [org.jboss.classloader.spi.ClassLoaderSystem] (RMI TCP Connection(2)-127.0.0.1) DefaultClassLoaderSystem at 113981b registered domain=ClassL
oaderDomain at ecf5c7{name=jboss.j2ee:extension=LoaderRepository,service=EARDeployment,url='testscopedrar-nojbossapp.ear' parentPolicy=AFTER_BUT_JAVA_BEFORE parent=ClassL
oaderDomain at 1672bbb{DefaultDomain}}
> Setting isolated=true on EarClassLoaderDeployer does not work
> -------------------------------------------------------------
>
> Key: JBAS-6600
> URL: https://jira.jboss.org/jira/browse/JBAS-6600
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ClassLoading
> Affects Versions: JBossAS-5.0.0.GA, JBossAS-5.0.1.GA
> Environment: JBossAS-5.0 GA and JBossAS-5.0.1.GA, Sun Java 1.5
> Reporter: jaikiran pai
> Assignee: Adrian Brock
> Fix For: JBossAS-5.1.0.CR1, JBossAS-5.0.2.GA, JBossAS-6.0.0.Alpha1
>
> Attachments: Isolated_Ear.patch
>
>
> JBossAS-5 allows each EAR to have its own isolated classloader, by setting the isolated flag to true in the EARClassLoaderDeployer (%JBOSS_HOME%/server/default/deployers/ear-deployer-jboss-beans.xml):
> <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.
> -->
> <property name="isolated">true</property>
> </bean>
> However, this does not work. The classloaders for the EARs are not isolated. Please see the referenced forum thread for the complete details and the patch.
--
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