Thanks heaps, This was the problem (the first answer with the JVM property).
It seems that when I was upgrading the installations and transferring the customizations we'd made to 3.2.3 startup scripts, I made a silly mistake with customizing the JAVA_OPTS variable. Instead of the usual windows property setting, "set VAR=VALUE", I suffered an attack of windows/unix dislexia and put in "VAR=VALUE". What this meant was that the rmi variable not being set, which is exactly what you thought it was. Sorry for posting this as a bug, I guess I'll be eating some bad tasting humble pie for a week or more. Cheers, David L View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839348#3839348 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839348 ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
