farming with .jar in ./farm/ doesn't work

[kaobe]

Hello Forum,

I'm setting up a clustered jboss with clusterwide hot deploy via farming.
Until now my .jar took place in the ./deploy/ folder. But if I set the URLs attribute in farm-service.xml on this directory, both nodes I work with break down at deploy time.
If I change the place of the .jar to the ./farm/ directory, the jboss instance does not start properly. The first error is

*******************
16:04:43,776 INFO [MainDeployer] Deployment of package: file:/C:/JBCluster/server1/jboss-3.2.1/server/gvp/farm/catalog.jar is waiting for an appropriate deployer.
16:04:43,776 ERROR [FarmMemberService] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@56b1a320 { url=file:/C:/JBCluster/server1/jboss-3.2.1/server/gvp/farm/catalog.jar }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/JBCluster/server1/jboss-3.2.1/server/gvp/farm/catalog.jar
lastDeployed: 1059055483766
lastModified: 1059055483716
mbeans:
]Incompletely deployed packages:
.....
*******************

I've tried to set the URLs attribute to ./farm/, too. But that did not work either.

Could it be I have to change the ejb-jar.xml or another file of the jboss configuration? Or do I have to put other files into the ./farm/ folder, too?

I tried to find a solution with google, in this forum, but I haven't found one possible solution. Perhaps one of you could help me? Thank you very much in advance!!!

Peter

[darranl]

You do not want to change the farm-service.xml to scan the deploy directory, that will lead you to loads of other problems.

Generally the JBoss default configurations work out of the box so unless you are changing multicast addresses or partition names you should not need to edit any of the files supplied with JBoss.

Can you deploy your application on both nodes by putting it in the deploy folder manually on both nodes? I know that you want it to be deployed by using farming but that will test that there are no problems with your application.

[kaobe]

Hi darranl,

the JBoss server runs without problems if I deploy it only in the deploy folder. If my .jar is in the farm folder, the depoy fails with the exception above.
At first I didn't change anything in the farm-service.xml except the partition name. It works and hot-deploys the .jar on the other node, but the JBoss instance doesn't work.
I'm wondering why the server starts without problems if I have all files in the deploy folder, and fails to start if I have one of the files (the .jar) in the farm folder.
Do you have any other tips for me?

Thank you very much for your help.

Peter

[slaboure]

This is a dependency issues between deployment. Please try 3.2.2RC2

[kaobe]

Thank you very much.

I solved it by adding all possible services in the tags and then removing them for tests.

Now it works.

It was this dependency:

jboss.jca:service=CachedConnectionManager

Thanks all!!

Peter