>> ... which also seems to deploy flawlessly, on both machines (in >> the default/deploy directory)
> I guess it is wrong here. a new folder JBOSS_HOME/server/default/farm has > most probably been created: use this one. I figured out that one ... but still no go ... (I now also use the `run --configuration all` option so it's actually JBOSS_HOME/server/all/farm) >> java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces >> commented out > don't do that: in-VB JNDI resolution will no more be optimised. ok, I tried both, nothing happens on the "other" server when the jndi.properties has it's "factory defaults" either ... But thanks, anyway! Should the farm-service.xml be identical on the two machines, or are one of the xml-fields some node-identificator indicating a unique ID for the farm-node? -- [EMAIL PROTECTED] _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
