[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1663) deploying multiple examples on Tomcat fails from colliding Ejbs (TimerServiceDispatcher)

Matt Drees (JIRA) jira-events at lists.jboss.org
Sat Jul 14 05:16:03 EDT 2007


deploying multiple examples on Tomcat fails from colliding Ejbs (TimerServiceDispatcher)
----------------------------------------------------------------------------------------

                 Key: JBSEAM-1663
                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1663
             Project: JBoss Seam
          Issue Type: Bug
    Affects Versions: 2.0.0.BETA1
         Environment: tomcat 6.0.13, embedded-jboss-beta2, seam-20070714.0506
            Reporter: Matt Drees
            Priority: Minor


When I deploy jboss-seam-booking and jboss-seam-dvd, the second app to be deployed fails with the following exception:

org.jboss.deployers.spi.DeploymentException: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3 is already registered
        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 org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:128)
        at org.jboss.embedded.tomcat.WebinfScanner.lifecycleEvent(WebinfScanner.java:88)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4236)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
        at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
        at org.apache.catalina.core.StandardService.start(StandardService.java:516)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3 is already registered
        at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:80)
        at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:465)
        at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:410)
        at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:392)
        at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:358)
        at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:313)
        at org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:157)
        ... 31 more

I tried adding jboss-app.xml to the jar for each project, from seeing from the forum something about scoped classloading, but that didn't help any.

-- 
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

        



More information about the seam-issues mailing list