[
https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu...
]
Galder Zamarreno commented on JBIDE-3475:
-----------------------------------------
node1/server1.log:
server.log:5763:2008-12-31 16:01:08,462 33229 INFO [org.jboss.ejb3.EJB3Deployer]
(ScannerThread:) Deployed:
file:/home/galder/jboss/sandbox/git/.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-251304_1/deploy/acme-haejb3.jar
...
server.log:5956:2008-12-31 16:01:08,586 33353 INFO [org.jboss.ejb3.EJB3Deployer]
(ScannerThread:) Deployed:
file:/home/galder/jboss/sandbox/git/.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-251304_2/deploy/acme-haejb3.jar
Second deployment should have gone to node2.
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
Priority: Critical
Fix For: 3.0.0.GA
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