We don't have a switch to turn clustering on/off. Best way is to build from "default" and then add the service libarary that you need.
Thank you for your reply.
We did start with the "default" configuration, and added our own ejbs, wars etc to the deploy directory. I hope this is what you mean by "build from default" and add a "service library."
Have I understood your recommendation properly?
there is no dependency on clustering in the "default" configuration. If you started with this configuration, it seems likely that you added something which does have a clustering dependency.
You note that you removed cluster-service.xml. This configuration file isn't included in the default configuration. If you had to remove it, did you start with the "all" configuration instead?
Ahh. Thank you Ben and Jerry!
I now think the issue was the install option I selected when I unpacked the 4.0.3 download. It creates a deploy directory called "default" but I must have clicked the "all" radio button and got that configuration.
I had missed that change in directory structure, and was accustomed to the old install where we had separate directories for "default," "all" and "minimal" configurations.
This information may be of use to others who have posted questions with keywords such as: disable clustering, multicast, UDP, standalone deployment.