[
http://jira.jboss.com/jira/browse/JBCLUSTER-49?page=comments#action_12376688 ]
Scott Marlow commented on JBCLUSTER-49:
---------------------------------------
The vote count for this bug is zero and a different model for deploying applications to
the cluster is supposed to be introduced in the 5.x release timeframe. I'm leaving
this open as it is a bug, however, I'm not planning on fixing it at this point.
An application that is "farm" undeployed from the cluster
could come back into the cluster.
-------------------------------------------------------------------------------------------
Key: JBCLUSTER-49
URL:
http://jira.jboss.com/jira/browse/JBCLUSTER-49
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: Q2Y5
Environment: any
Reporter: Scott Marlow
Assigned To: Scott Marlow
Fix For: Bugs
An application that is "farm" undeployed from the cluster could come back into
the cluster. Steps to reproduce:
a. Create a cluster with more than one node. Lets assume three server nodes named {
node1, node2, node3 }
b. Deploy an application to the cluster, I used WineDemo.war.
c. Bring node3 down.
d. Delete WineDemo.war from the cluster. Note that it didn't get deleted from
node3's farm folder as node3 is down.
e. Bring node3 back up, WineDemo.war is still running on node3.
The workaround for this issue is to manually remove WineDemo.war from node3 before
bringing it back up.
A secondary problem occurs you then bring node2 down and back up. We will deploy
WineDemo.war on node2 (pulled from node3).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira