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

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448265#action_12448265 ] 

Rob Stryker commented on JBIDE-3475:
------------------------------------

wow. Wow. So... I've got some stuff to report. I don't know that this is a tooling error. But either way, it's a big issue. My example below doesn't even deploy anything. It doesn't need to. This is a clear and present JMX issue.

My methodology is as follows:

1) set up the lo2 and lo3 as mentioned
2) create ONE server using lo2, start it up, observe that it starts properly. Everything's pretty cool.
3) Use the attached JAVA file (modify it of course) to attempt to use JMX to SHUTDOWN a server on lo3. Remember, there is NO server running on lo3 currently. The only server running is on lo2.
4) Watch the mayham.

What happens is:
 - the mainOutput.txt attachment shows what happens when MyMain.java is run.
 - the runningServer_server.log attachment shows what happens to the server.

If you're too lazy to read the attachments, basically, the MyMain fails, BUT, the server on lo2 proceeds to shut down anyway!!!

Any thoughts on who we should ping over this? 

> 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: Snjezana Peco
>            Priority: Blocker
>             Fix For: 3.0.0.CR2
>
>         Attachments: 20090116.zip, acme-haejb2.jar, 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