[
http://jira.jboss.com/jira/browse/JBAS-4206?page=all ]
Scott M Stark closed JBAS-4206.
-------------------------------
Resolution: Done
The mc 2.0.0.Beta3.1 release includes updated MainDeployer handling of the tcl. It looks
first to the unit class loader and if null, to the deployer class loader.
HDScanner processing does not use correct TCL
---------------------------------------------
Key: JBAS-4206
URL:
http://jira.jboss.com/jira/browse/JBAS-4206
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment services
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta2
Trying to hotdeploy content that needs classes from outside of the bootstrap class loader
fails:
18:41:40,574 ERROR [EJBRegistrationDeployer] Error during deployment:
vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deploy/aop-mc-jmxtest.jar
org.jboss.deployers.spi.DeploymentException: java.lang.RuntimeException:
javax.naming.NoInitialContextException: Cannot instantiate class:
org.jnp.interfaces.NamingContextFactory [Root exception is
java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
at
org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:167)
at
org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
at
org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170)
at
org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592)
at
org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476)
at
org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406)
at sun.reflect.GeneratedMethodAccessor102.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:121)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:110)
at
org.jboss.profileservice.aop.MainDeployerAspect.process(MainDeployerAspect.java:53)
at
org.jboss.aop.advice.org.jboss.profileservice.aop.MainDeployerAspect_z_process_1601866242.invoke(MainDeployerAspect_z_process_1601866242.java)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at AOPContainerProxy$0.process(AOPContainerProxy$0.java)
at
org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:247)
at
org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
MainDeployerImpl.process should probably be installing the current deployer class loader
as the TCL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira