Ok, a bad local config must have been that case because after a clean build and check of the jndi.properties the test is running fine with the cluster present.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Sacha Labourey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 23, 2002 12:41 AM Subject: RE: [JBoss-dev] Why is this being dumped out? > > I'm running the default configuration so I doubt it unless the presence > > of a cluster dictates this. This totally screwed up the testsuite run. > > It could also happen if your client JNDI config is wrong (host not > resolvable, etc.). In this case, if no JNDI service is found, a multicast > discovery packet is sent to find an available JBoss HA-JNDI instance. If > found, you will receive a HA-JNDI proxy, hence the message. > > Cheers, > > > Sacha _______________________________________________________________ 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-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
