[jboss-user] [Clustering/JBoss] - Farm deployment errors with large WAR files

Hi, I am having a problem using the farm deployment model with a large WAR file. My setup: two ubuntu 9.04 servers running sun java 1.6.0_14 and JBoss AS 5.1.0_GA The two systems are connected through a 1 GB link and the default clustering settings are used (meaning UDP multicast, some settings are overridden on startup) Here is the startup command for each server: Server1 ./run.sh -c all -b 10.200.90.105 -Djboss.messaging.ServerPeerID=10 -Djboss.messaging.groupname=TestPostOffice -g TestPartition1 ./run.sh -c all -b 10.200.90.105 -Djboss.messaging.ServerPeerID=11 -Djboss.messaging.groupname=TestPostOffice -g TestPartition1 My first test worked fine, I was using a small war file (410K) pclark@bks:~/development/servers/jboss-5.1.0.GA/server/all/farm$ ls -l total 440 -rw-r--r-- 1 pclark pclark 6830 2009-06-30 11:12 cluster-examples-service.xml -rw-r--r-- 1 pclark pclark 441162 2009-07-02 12:02 test.war And the file deployed on both servers with: 12:03:50,614 INFO [TomcatDeployment] deploy, ctxPath=/test However, the problem comes in with a larger war file. The second test was with a 120MB file. The file deploys on one server, but not on the other. It fails with the error: 2009-07-02 11:16:57,801 INFO [org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler] (HDScanner) Unable to acquire local lock: Unable to acquire lock as it is held by 10.200.90.105:1099 2009-07-02 11:16:57,801 ERROR [org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository] (HDScanner) getModifiedDeployments(): Cannot acquire local lock In addition, if I bring the master server up by itself and deploy through the farm directory, it deploys successfully. I will then bring up a second server and it will deploy successfully. However, if I bring them all up at once it fails with the locking error. Or if I try to deploy once all servers in the cluster are up it fails with the locking error. We were thinking that the size of the file was the problem. So we iteratively scaled down the war file until we could get it to successfully deploy. It appears that the limit is around 2MB. Does anyone know what might be happening here? Are there any ideas on how to get the farm deployment to work reliably with large war files? Thanks for your time, Patrick View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241567#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...