[jboss-jira] [JBoss JIRA] Closed: (JBCLUSTER-35) hot deployment: new files are not replicated throughout the cluster
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Sat Apr 12 12:19:54 EDT 2008
[ http://jira.jboss.com/jira/browse/JBCLUSTER-35?page=all ]
Brian Stansberry closed JBCLUSTER-35.
-------------------------------------
Fix Version/s: Q3Y5
(was: Bugs)
Resolution: Done
> hot deployment: new files are not replicated throughout the cluster
> -------------------------------------------------------------------
>
> Key: JBCLUSTER-35
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-35
> Project: JBoss Clustering
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: Q2Y5
> Environment: SuSE Linux 9.1 professional, JBoss 3.2.6, 4-node cluster without HTTP session replication (just farming)
> Reporter: Stefan Meier
> Assigned To: Scott Marlow
> Priority: Minor
> Fix For: Q3Y5
>
>
> Once I deploy a new version of an existing app (e.g. replace the respective file in $JBOSS_HOME/server/all/farm), the file gets correctly deleted on all other nodes i the cluster, but the new file does not get distributed correctly.
> if I do my deployment in three steps
> - undeploy app.
> - wait a few secs (to give the other nodes time to catch up)
> - deploy app.
> everything works fine ... but that's not how I'd like to do hot deployment :)
--
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
More information about the jboss-jira
mailing list