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

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3475: ----------------------------------------- Rob, I've verified latest trunk and still does not work. Very easy to replicate: 1. Download eclipse-jee-ganymede-SR1-linux-gtk.tar.gz 2. Install latest from http://download.jboss.org/jbosstools/updates/nightly/trunk 3. Create two runtime+servers from EAP 4.3.0.GA_CP03, one called jbide3475_1 and the other jbide3475_2 based on 'all' configuration. 4. Double click on 4.3.0.ga.cp03-jbide3475_1 and change hostname to lo2 (see "Setting up a cluster with localhost addresses" section from http://www.jboss.org/community/docs/DOC-10211) 5. Double click on 4.3.0.ga.cp03-jbide3475_2 and change hostname to lo3 (see "Setting up a cluster with localhost addresses" section from http://www.jboss.org/community/docs/DOC-10211) 6. Click on "Open Launch configuration" for 4.3.0.ga.cp03-jbide3475_2 and add -Djboss.messaging.ServerPeerID=1 VM argument. 7. Take the attached .jar and deploy it in 4.3.0.ga.cp03-jbide3475_1 first and wait for the server to finish starting up. 8. Start 4.3.0.ga.cp03-jbide3475_2 and you'll see the phenomenon explained. -- 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