[esb-issues] [JBoss JIRA] Updated: (JBESB-2874) Deployers do not cleanly represent dependencies

Daniel Bevenius (JIRA) jira-events at lists.jboss.org
Fri Jun 18 08:22:46 EDT 2010 

     [ https://jira.jboss.org/browse/JBESB-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Bevenius updated JBESB-2874:
-----------------------------------

    Attachment: redeploy-issue.jar


This is the example that I've been using. Deploy domain_model first and then service1 using mvn install -Desb.deploy.dir=your_deploy_dir.
Then redeploy the domain_model and you should get the following in the server console log:

14:13:31,188 INFO  [EsbWsdlDeployer] Generating wsdl url : vfsmemory://service1-1.0_WSDL/WEB-INF/wsdl/Sample/Service1-1.0.wsdl
14:13:31,213 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=service1-1.0,endpoint=Sample_Service1-1.0
14:13:31,330 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/Users/danbev/work/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/service1-1.0.esb/ state=PreReal mode=Manual requiredState=Installed
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/Users/danbev/work/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/service1-1.0.esb/
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)
Caused by: org.jboss.wsf.spi.deployment.WSFDeploymentException: java.lang.IllegalStateException: BaseClassLoader at 5a5bed02{vfszip:/Users/danbev/work/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/service1-1.0.esb/} classLoader is not connected to a domain (probably undeployed?) for class org.jboss.wsf.stack.jbws.EndpointServlet
	at org.jboss.wsf.spi.deployment.WSFDeploymentException.rethrow(WSFDeploymentException.java:52)
	at org.jboss.wsf.container.jboss50.deployment.tomcat.ModifyWebMetaDataDeploymentAspect.create(ModifyWebMetaDataDeploymentAspect.java:52)
	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
	at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:76)
	at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
	... 24 more
Caused by: java.lang.IllegalStateException: BaseClassLoader at 5a5bed02{vfszip:/Users/danbev/work/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/service1-1.0.esb/} classLoader is not connected to a domain (probably undeployed?) for class org.jboss.wsf.stack.jbws.EndpointServlet
	at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:793)
	at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:441)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
	at org.jboss.wsf.container.jboss50.deployment.tomcat.WebMetaDataModifierImpl.modifyMetaData(WebMetaDataModifierImpl.java:134)
	at org.jboss.wsf.container.jboss50.deployment.tomcat.WebMetaDataModifierImpl.modifyMetaData(WebMetaDataModifierImpl.java:57)
	at org.jboss.wsf.container.jboss50.deployment.tomcat.ModifyWebMetaDataDeploymentAspect.create(ModifyWebMetaDataDeploymentAspect.java:48)
	... 29 more




> Deployers do not cleanly represent dependencies
> -----------------------------------------------
>
>                 Key: JBESB-2874
>                 URL: https://jira.jboss.org/browse/JBESB-2874
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployment
>    Affects Versions: 4.7
>            Reporter: Kevin Conner
>            Assignee: Magesh Kumar B
>             Fix For: 4.9
>
>         Attachments: redeploy-issue.jar
>
>
> The deployers create a separate object to represent the ESB deployment, expressing the contained dependencies, but any forced restart of this object (due to dependencies) does not redo any of the work contained in the deployer.
> We now have a lot of work which, as a consequence, misses out on this process.
> - ebws
> - http gateway
> - property substitution
> We need to move all this functionality into a separate object which can cleanly take part in the dependency process.

-- 
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 esb-issues mailing list