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.
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.
This is a dependency issues between deployment. Please try 3.2.2RC2
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: