Short Description: Farm doesn't copy jars to other servers correctly about 30% of the time.
Situation: We've got 4 JBoss servers clustered together. We're using the original 3.0.0 release of JBoss. We have about 7 stateless session beans and 4 entity beans. Detailed Description: We have the farm service xml in place and probably about 70% of the time everything works fine. For the other 30% of the time when we copy the 11 jar files up to the base machine the farm copies them out to the other machines and on at least one machine we get a corrupted zip file exception. So we have to delete that bean back out of the base machine and deploy it again. So the more machines we add the more possibilities for this error to occur and the longer it takes to put up new code to the cluster. Has anyone else seen this before? The Question/Solution: We're thinking of upgrading as the problem may already have been fixed. Has the Clustering/Farm/JavaGroups code been stabilized or improved from 3.0.0 to 3.0.6? Finally: Let me say that this is a little annoying, but so far that's it. Just annoying, not a show stopper, or anything yet. And all things considered, JBoss (including clustering and farming) has been great! So thanks in advance for any help, and THANKS to all the developers who contributed their time to JBoss. -Jason ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
