[jboss-jira] [JBoss JIRA] Commented: (JBAS-4422) org.jboss.test.util.test.TwiddleUnitTestCase can't connect to host

[ http://jira.jboss.com/jira/browse/JBAS-4422?page=comments#action_12372390 ] Richard Achmatowicz commented on JBAS-4422: ------------------------------------------- 1. Twiddle is a command line tool which allows sending MBeanServer commands to an application server and receiving the results. Twiddle has a -s <hostname> option. Using this option tells Twiddle to use that hostname when doing a JNDI lookup to get the MBeanServerConnection proxy it needs to communicate with the MBeanServer. Use of the -s option to cause JNDI to do a lookup on the testsuite AS instance node0 was commented out in TwiddleUnitTestCase: if (isWindows()) { command.add("cmd"); command.add("/C"); command.add("twiddle"); //command.add("-s"); //command.add(getServerHost()); command.addAll(Arrays.asList(args)); } else { command.add("/bin/sh"); command.add("-c"); String twiddleCmd = "./twiddle.sh "; //twiddleCmd += "-s "; //twiddleCmd += getServerHost(); twiddleCmd += makeTwiddleArgs(args); command.add(twiddleCmd); } Reinstating the -s option fixes the problem with the test case, as the command getServerHost() returns the correct name for the host on which the AS was started (e.g. localhost, or 192.23.1.21), the JNDI lookup succeeds, the MBeanServerConnection proxy is obtained, and the MBeanServerCommand is executed. I have checked this on Windows. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira