[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2136) A failed singleton bean redeployment causes "Already registered" errors

jaikiran pai (JIRA) jira-events at lists.jboss.org
Sun Aug 1 09:20:49 EDT 2010


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

jaikiran pai resolved EJBTHREE-2136.
------------------------------------

    Component Fix Version(s): singleton:1.0.0-alpha-11
               Fix Version/s: bom-as6-0.2.0
                  Resolution: Done


Fixed http://github.com/jbossejb3/jboss-ejb3-singleton/commit/d9dc7f5a27f502cbcbbf5d0152d9f9c927d95600


> A failed singleton bean redeployment causes "Already registered" errors 
> ------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2136
>                 URL: https://jira.jboss.org/browse/EJBTHREE-2136
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: singleton
>         Environment: JBoss AS 6.0.0.M4 (bom-as6:0.2.0-alpha-10)
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: bom-as6-0.2.0
>
>
> If a deployment of a singleton bean fails and the user then redeploys the application (after fixing the original error), the redeployment fails with "Already registered" errors for the singleton container.
> Please refer to the referenced forum thread for the entire details, including the root cause of this issue.

-- 
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 jboss-jira mailing list