[jboss-jira] [JBoss JIRA] Updated: (JBAS-6600) Setting isolated=true on EarClassLoaderDeployer does not work
Shelly McGowan (JIRA)
jira-events at lists.jboss.org
Wed Apr 8 23:30:22 EDT 2009
[ https://jira.jboss.org/jira/browse/JBAS-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan updated JBAS-6600:
---------------------------------
We're seeing regressions in the TCK runs when a .rar is packaged in an ear (JBCTS-905). The cts config, based off standard config, has the EarClassLoaderDeployer property isolated set to true in deployers/-deployer-jboss-beans.xml resulting in ClassNotFoundException during deployment:
23:24:31,168 INFO [MainDeployer] deploy, url=file:/tmp/JCAAdmin8403871540741745946-ds.xml
23:24:31,196 ERROR [ManagedConnectionFactoryDeployment] Could not find ManagedConnectionFactory class: com.sun.ts.tests.common.connector.whitebox.LocalTxManagedConnectionFactory
java.lang.ClassNotFoundException: com.sun.ts.tests.common.connector.whitebox.LocalTxManagedConnectionFactory from BaseClassLoader at 1abbcda{VFSClassLoaderPolicy at 1fba08e{name=vfsfile:/tmp/JCAAdmin8403871540741745946-ds.xml domain=ClassLoaderDomain at 11d491f{name=jboss.j2ee:extension=LoaderRepository,service=EARDeployment,url='ejb_Deployment.ear' parentPolicy=AFTER_BUT_JAVA_BEFORE parent=ClassLoaderDomain at 1732ed2{DefaultDomain}} roots=[MemoryContextHandler at 15338041[path= context=vfsmemory://3j001-bift8e-ftavwdr5-1-ftavy4i2-4x real=vfsmemory://3j001-bift8e-ftavwdr5-1-ftavy4i2-4x]] delegates=null exported=[] <IMPORT-ALL>NON_EMPTY}}
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:422)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment.startService(ManagedConnectionFactoryDeployment.java:344)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124)
Changing the property to false, the deployment is successful and the test passes.
> 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: Ales Justin
> 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