[seam-issues] [JBoss JIRA] Moved: (JBSEAM-4803) Seam2 WAR applications with Boss6 throw javax.naming.NameAlreadyBoundException thrown for TimerServiceDispatcher/local

[Alexey Kazakov (JIRA)]

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

Alexey Kazakov moved JBIDE-8774 to JBSEAM-4803:
-----------------------------------------------

              Project: Seam 2  (was: Tools (JBoss Tools))
                  Key: JBSEAM-4803  (was: JBIDE-8774)
    Affects Version/s: 2.2.1.Final
                           (was: 3.2.0.Final)
             Assignee:     (was: Rob Stryker)
          Component/s: EJB3
                           (was: ejb3)


> Seam2 WAR applications with Boss6 throw javax.naming.NameAlreadyBoundException thrown for TimerServiceDispatcher/local
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4803
>                 URL: https://issues.jboss.org/browse/JBSEAM-4803
>             Project: Seam 2
>          Issue Type: Bug
>          Components: EJB3
>    Affects Versions: 2.2.1.Final
>         Environment: JBoss Developer Studio 4.0.0.GA with 64 bit Java 1.6.0_24-b07 running on Windows 7 x64 with SP1
> SEAM 2.2.1.Final
> JBoss 6.0.0.Final
>            Reporter: Gerry Matte
>              Labels: JNDI
>         Attachments: boot.log, server.log
>
>
> I created two application WARs with totally different datasources/persistence contexts.  The first one is using persistence but second one is not using persistence. 
> 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.
> Both applications were created using the Eclipse "New SEAM Project" wizard and configured as a WAR application rather than an EAR application.  (I'm actually using JBoss Developer 4.0).
> I made zero changes to any XML files other than web.xml to define some servlets and configure authentication using JBoss's JAAS container Authentication.
> 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.
> 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

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira