Farm Deployment fails for large WARs in EAP 5

Issue

• Deployment of small wars  to the farm directory seems to work fine. But deployment of large wars, for example 66MB, appears to fail.  The log captured in the secondary node when this happens is as follows

  2010-09-20 11:29:40,448 INFO  [org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler] (HDScanner) Unable to acquire local lock: Unable to acquire lock as it is held by 10.20.30.40:1099
  2010-09-20 11:29:40,449 ERROR [org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository] (HDScanner) getModifiedDeployments(): Cannot acquire local lock
  2010-09-20 11:31:40,478 INFO  [org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler] (HDScanner) Unable to acquire local lock: Unable to acquire lock as it is held by 10.20.30.40:1099
  2010-09-20 11:31:40,478 ERROR [org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository] (HDScanner) getModifiedDeployments(): Cannot acquire local lock
  2010-09-20 11:33:40,509 INFO  [org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler] (HDScanner) Unable to acquire local lock: Unable to acquire lock as it is held by 10.20.30.40:1099
  2010-09-20 11:33:40,509 ERROR [org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository] (HDScanner) getModifiedDeployments(): Cannot acquire local lock