[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-3475) New deployment mechanism not working correclty on clustered or multi-server envs.

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-3475:
---------------------------------------

    Fix Version/s: 3.0.0.CR2
                       (was: 3.0.0.GA)
         Assignee: Rob Stryker
         Priority: Blocker  (was: Critical)


talked with Galder and this sounds like a big blocker for any users that have more than one AS setup (which is not uncommon).



> New deployment mechanism not working correclty on clustered or multi-server envs.
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-3475
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3475
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.CR2
>            Reporter: Galder Zamarreno
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.0.0.CR2
>
>         Attachments: jbide3475.zip
>
>
> There's something not working correctly with the new deployment mechanism:
> I have a cluster of 2 nodes with an clustered EJB3 application deployed (SLSBs, SFSBs, Entities...etc). 
> When I start the 1st node, it works perfectly and after startup being completed, ear is deployed without
> any issues. 
> After deployment is complete, I start the 2nd node and the EJB3 application is deployed again in the 1st
> node and the 2nd node has no deployment whatsoever.
> See attached logs + ear app.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira