7 Replies Latest reply on Jun 21, 2011 7:53 PM by H G

    Multiple standalone WAR

    Swen Vogel Newbie

      Hi,


      i want to deploy two standalone Seam (2.2.1.Final) WAR applications into JBoss AS (6.0.0.Final)


      The problem is that both applications wants to register EJB's to the same global JNDI names.
      This leads to a javax.naming.NameAlreadyBoundException exception when the second
      app is loaded.


      I already tried to change the jndiPattern in the components.properties, without effects.


      From the server logs:


      .... neonis-web.war is loaded
      
      16:43:44,671 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=neonis-web.war,name=EjbSynchronizations,service=EJB3
      16:43:44,671 INFO  [JBossASKernel]   with dependencies:
      16:43:44,671 INFO  [JBossASKernel]   and demands:
      16:43:44,671 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService; Required: Described
      16:43:44,671 INFO  [JBossASKernel]      jboss-switchboard:appName=neonis-web,module=neonis-web; Required: Create
      16:43:44,671 INFO  [JBossASKernel]   and supplies:
      16:43:44,671 INFO  [JBossASKernel]      jndi:EjbSynchronizations
      16:43:44,671 INFO  [JBossASKernel]      jndi:EjbSynchronizations/local
      16:43:44,671 INFO  [JBossASKernel]      jndi:EjbSynchronizations/local-org.jboss.seam.transaction.LocalEjbSynchronizations
      16:43:44,671 INFO  [JBossASKernel]      Class:org.jboss.seam.transaction.LocalEjbSynchronizations
      16:43:44,671 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=neonis-web.war,name=EjbSynchronizations,service=EJB3) to KernelDeployment of: neonis-web.war
      16:43:44,687 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=neonis-web.war,name=TimerServiceDispatcher,service=EJB3
      16:43:44,687 INFO  [JBossASKernel]   with dependencies:
      16:43:44,687 INFO  [JBossASKernel]   and demands:
      16:43:44,687 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService; Required: Described
      16:43:44,687 INFO  [JBossASKernel]      jboss-switchboard:appName=neonis-web,module=neonis-web; Required: Create
      16:43:44,687 INFO  [JBossASKernel]      jboss-injector:topLevelUnit=neonis-web.war,unit=neonis-web.war,bean=TimerServiceDispatcher; Required: Described
      16:43:44,687 INFO  [JBossASKernel]   and supplies:
      16:43:44,687 INFO  [JBossASKernel]      Class:org.jboss.seam.async.LocalTimerServiceDispatcher
      16:43:44,687 INFO  [JBossASKernel]      jndi:TimerServiceDispatcher
      16:43:44,687 INFO  [JBossASKernel]      jndi:TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher
      16:43:44,687 INFO  [JBossASKernel]      jndi:TimerServiceDispatcher/local
      
      .... seamTest.war is loaded
      
      16:44:05,973 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=seamTest.war,name=EjbSynchronizations,service=EJB3
      16:44:05,973 INFO  [JBossASKernel]   with dependencies:
      16:44:05,973 INFO  [JBossASKernel]   and demands:
      16:44:05,973 INFO  [JBossASKernel]      jboss-switchboard:appName=seamTest,module=seamTest; Required: Create
      16:44:05,973 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService; Required: Described
      16:44:05,973 INFO  [JBossASKernel]   and supplies:
      16:44:05,973 INFO  [JBossASKernel]      jndi:EjbSynchronizations
      16:44:05,988 INFO  [JBossASKernel]      jndi:EjbSynchronizations/local
      16:44:05,988 INFO  [JBossASKernel]      jndi:EjbSynchronizations/local-org.jboss.seam.transaction.LocalEjbSynchronizations
      16:44:05,988 INFO  [JBossASKernel]      Class:org.jboss.seam.transaction.LocalEjbSynchronizations
      16:44:05,988 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=seamTest.war,name=EjbSynchronizations,service=EJB3) to KernelDeployment of: seamTest.war
      16:44:05,988 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=seamTest.war,name=TimerServiceDispatcher,service=EJB3
      16:44:05,988 INFO  [JBossASKernel]   with dependencies:
      16:44:05,988 INFO  [JBossASKernel]   and demands:
      16:44:05,988 INFO  [JBossASKernel]      jboss-switchboard:appName=seamTest,module=seamTest; Required: Create
      16:44:05,988 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService; Required: Described
      16:44:05,988 INFO  [JBossASKernel]      jboss-injector:topLevelUnit=seamTest.war,unit=seamTest.war,bean=TimerServiceDispatcher; Required: Described
      16:44:05,988 INFO  [JBossASKernel]   and supplies:
      16:44:05,988 INFO  [JBossASKernel]      Class:org.jboss.seam.async.LocalTimerServiceDispatcher
      16:44:05,988 INFO  [JBossASKernel]      jndi:TimerServiceDispatcher
      16:44:05,988 INFO  [JBossASKernel]      jndi:TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher
      16:44:05,988 INFO  [JBossASKernel]      jndi:TimerServiceDispatcher/local
      



        • 1. Re: Multiple standalone WAR
          Swen Vogel Newbie

          I have found this related thread, but the applications are packaged as EAR and not as WAR archives:


          http://seamframework.org/Community/JavaxnamingNameAlreadyBoundExceptionForEjbSynchronizations

          • 2. Re: Multiple standalone WAR
            Serkan Eskici Novice

            I also have two WAR files deployed on JBoss 5.1 and in the beginning I had th same problem as yours, but after I gave unique names for the persistence units in pErsistence.xml I don't get the error anymore.

            • 3. Re: Multiple standalone WAR
              Swen Vogel Newbie

              Ok to revalidate everything i generated two WAR projectes seamTest1 and seamTest2 with the eclipse jboss tools and changed the persistence configuration:



              seamTest1


              persistence.xml
              
              <persistence-unit name="seamTest1" transaction-type="JTA">
                <jta-data-source>java:/seamTest1Datasource</jta-data-source>
                ....
                
              components.xml
              
                <persistence:entity-manager-factory
                  name="entityManagerFactory" persistence-unit-name="seamTest1" />
                ...
              



              seamTest2


              persistence.xml
              
              <persistence-unit name="seamTest2" transaction-type="JTA">
                <jta-data-source>java:/seamTest2Datasource</jta-data-source>
                ....
                
              components.xml
              
              <persistence:entity-manager-factory
                name="entityManagerFactory" persistence-unit-name="seamTest2" />
               ...
              



              But this not fix the bug. The JNDI names from the datasources are different
              and work fine. The problem are the JNDI names of EjbSynchronizations and the
              TimerServiceDispatcher EJB's that are registered by seam itself.


              The EJB's are bound without any project/application path!


              • 4. Re: Multiple standalone WAR
                Gerry Matte Newbie

                I have this exact same issue. 
                Two WARs with totally different datasources/persistence contexts.
                My first application has been in production for a month or two.
                When I tried to implement a second SEAM 2.2.1.Final WAR application a javax.naming.NameAlreadyBoundException was thrown for TimerServiceDispatcher/local stating that local is already bound.


                This error did not happen on my development PC because I don't run multiple applications in the same jboss so there was no conflict between two application both trying to bind the same JNDI names.


                Below is the server log excerpt from my development PC when I startup just the single WAR.


                Note that I made zero changes to any XML files other than web.xml to define some servlets and configure JAAS Authentication.


                Currently, I am unable to implement a second WAR based application in this environment (Seam 2.2.1.Final on JBoss 6.0.0.Final).  I may soon have to downgrade my servers back to version 5.1 until this problem is fixed by someone.


                Gerry


                ................................................................................................................


                12:03:26,937 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=ss.war,name=TimerServiceDispatcher,service=EJB3
                12:03:26,953 INFO  [EJBContainer] STARTED EJB: org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
                12:03:26,984 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

                        TimerServiceDispatcher/local - EJB3.x Default Local Business Interface
                        TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher - EJB3.x Local Business Interface

                12:03:26,984 WARN  [TimerServiceContainer] EJBTHREE-2193: using deprecated TimerServiceFactory for restoring timers
                12:03:27,546 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=ss.war,name=EjbSynchronizations,service=EJB3
                12:03:27,546 INFO  [EJBContainer] STARTED EJB: org.jboss.seam.transaction.EjbSynchronizations ejbName: EjbSynchronizations
                12:03:27,561 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

                        EjbSynchronizations/local - EJB3.x Default Local Business Interface
                        EjbSynchronizations/local-org.jboss.seam.transaction.LocalEjbSynchronizations - EJB3.x Local Business Interface

                • 5. Re: Multiple standalone WAR
                  Swen Vogel Newbie

                  Hi,


                  i also could not find any fix for the problem. At first sight two WAR applications seems to work fine, except the error message.
                  But there a really big issues, for example with asynchronous events. In my case i raise an asynchronous event and send a
                  email with a configurable text. But a event raised in WAR-2 was processed by WAR-1 (the WAR that first registered the TimerService)
                  and the email contains the text that was configured in WAR-1.


                  In my opinion this is really a big bug! Finally i converted the WAR project to an EAR project with different class loader
                  definitions in each EAR. This works without problems in production.

                  • 6. Re: Multiple standalone WAR
                    Gerry Matte Newbie

                    I reported this issue as a bug and it has now been acknowledged as such.  See JIRA

                    • 7. Re: Multiple standalone WAR
                      H G Newbie

                      Hi,


                      I have the same problem! I'm using seam 2.2.2 and JBoss 6 final. The first WAR is using quarz. Both WARs are using Hibernate 3.6.3 with Hibernate Search 3.4 (to acomplish this  have to add jboss-classloading.xml). This is very frustrating, I can't find any solution. There will be soon any patch or some workaround??



                      jboss-classloading.xml of the second WAR:



                      <?xml version="1.0" encoding="UTF-8"?>
                      <classloading xmlns="urn:jboss:classloading:1.0"
                                               name="mofb.war"
                                         parent-first="false"
                                         domain="DefaultDomain"
                                         top-level-classloader="false"
                                         parent-domain="Ignored"
                                         export-all="NON_EMPTY"
                                         import-all="true">
                                         </classloading>



                      and this is the content of jboss-web.xml of the second WAR also:




                      <!DOCTYPE jboss-web PUBLIC
                          "-//JBoss//DTD Web Application 4.2//EN"
                          "http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd">
                      <jboss-web>  
                          <class-loading java2ClassLoadingCompliance="false">
                              <loader-repository>
                                  mofb:loader=mofb
                                  <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
                              </loader-repository>
                          </class-loading>
                      </jboss-web>
                      










                      18:24:40,015 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=mofb.war,name=TimerServiceDispatcher,service=EJB3
                      18:24:40,015 INFO  [EJBContainer] STARTED EJB: org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
                      18:24:40,031 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
                      
                              TimerServiceDispatcher/local - EJB3.x Default Local Business Interface
                              TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher - EJB3.x Local Business Interface
                      
                      18:24:40,046 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=mofb.war,name=TimerServiceDispatcher,service=EJB3 state=Create: java.lang.Runt
                      ss.seam.async.LocalTimerServiceDispatcher
                      Type: ProxyFactoryKey
                      Content: ProxyFactory/mofb/TimerServiceDispatcher/TimerServiceDispatcher/local
                      Type: EJB Container Name
                      Content: jboss.j2ee:jar=mofb.war,name=TimerServiceDispatcher,service=EJB3
                      Type: Proxy Factory is Local
                      Content: true
                      Type: Local Business Interface
                      Content: org.jboss.seam.async.LocalTimerServiceDispatcher
                       into JNDI at "TimerServiceDispatcher/local"
                              at org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.bind(JndiSessionRegistrarBase.java:939) [:1.0.11]
                              at org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.bind(JndiSessionRegistrarBase.java:919) [:1.0.11]
                              at org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.bind(JndiSessionRegistrarBase.java:908) [:1.0.11]
                              at org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.bindEjb(JndiSessionRegistrarBase.java:159) [:1.0.11]
                              at org.jboss.ejb3.session.SessionContainer.lockedStart(SessionContainer.java:223) [:1.7.17]
                              at org.jboss.ejb3.session.SessionSpecContainer.lockedStart(SessionSpecContainer.java:725) [:1.7.17]
                              at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:1105) [:1.7.17]
                              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_18]
                              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_18]
                              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_18]
                              at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_18]
                              at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.GA]
                              at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.GA]
                              at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.0.GA]
                              at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2
                              at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:894) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:641) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:182) [:2.2.0.GA]
                              at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58) [:2.2.0.GA]
                              at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.GA]
                              at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA]
                              at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]
                              at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.GA]
                              at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.GA]
                              at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1571) [:2.2.0.GA]
                              at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
                              at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
                              at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
                              at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
                              at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
                              at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151) [:0.2.2]
                              at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [:0.2.2]
                              at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
                              at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2]
                              at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87) [:0.2.2]
                              at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215) [:0.2.2]
                              at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159) [:0.2.2]
                              at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:112) [:0.2.2]
                              at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87) [:0.2.2]
                              at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2]
                              at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.0.0.Final]
                              at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
                              at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
                              at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
                              at java.lang.Thread.run(Thread.java:619) [:1.6.0_18]
                      Caused by: javax.naming.NameAlreadyBoundException: local
                              at org.jnp.server.NamingServer.bind(NamingServer.java:209) [:5.0.5.Final]
                              at org.jnp.server.NamingServer.bind(NamingServer.java:167) [:5.0.5.Final]
                              at org.jnp.interfaces.NamingContext.bind(NamingContext.java:652) [:5.0.5.Final]
                              at org.jnp.interfaces.NamingContext.bind(NamingContext.java:613) [:5.0.5.Final]
                              at org.jboss.util.naming.Util.bind(Util.java:105) [jboss-common-core.jar:2.2.17.GA]
                              at org.jboss.util.naming.Util.bind(Util.java:91) [jboss-common-core.jar:2.2.17.GA]
                              at org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.bind(JndiSessionRegistrarBase.java:934) [:1.0.11]
                              ... 80 more