[
https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-3475:
--------------------------------------
I can't reproduce this issue. Suppose that some additional settings needs to be done.
When I try to deploy acme-haejb3.jar to workspace/.metadata or to the server's deploy
folder, it is always deployed to only one node.
If I deploy acme-haejb3.jar to the server/all/farm folder, it is depoyed/undeployed
automatically to the both servers no matter when they were started.
It is possible to deploy some Seam WAR project in the following way:
- create two servers on two network nodes as described in
https://jira.jboss.org/jira/browse/JBIDE-3475?focusedCommentId=12448062#a...
- set deploy directory to server/all/farm
- create a Seam WAR project
- deploy *_ds.xml and do not deploy the project
- open the Project Archives view
- create a WAR archive
- deploy the archive to any of these two servers
The project will be deployed to the both nodes.
I have used 4.3.0.GA_CP03 (build: SVNTag=JBPAPP_4_3_0_GA_CP03 date=200810241616).
I couldn't create any EAR project archive due to an exception I got when I tried to
create it.
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, mainOutput.txt,
MyMain.java, server.log
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