Twiddle to bad host/port returns data! -------------------------------------- Key: JBAS-5157 URL: http://jira.jboss.com/jira/browse/JBAS-5157 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.0.4RC1 Environment: 4.0.3SP1, 4.2.1.GA, RedHat AS3.0 x86 (32-bit) Reporter: Peter Hufnagel Assigned To: Dimitris Andreadis Priority: Minor It appears that twiddle fails to return an error, seems to connect to a random instance (multiple instances on multiple IP's) and return the data for that instance. [phufnag@cipcrpdwas01 ext]$ telnet 3.122.100.14 1099 Trying 3.122.100.14... telnet: connect to address 3.122.100.14: No route to host telnet: Unable to connect to remote host: No route to host IP is actually unpingable on the network entirely, not plumbed on this box at all... [phufnag@cipcrpdwas01 ext]$ /data/apps/jdk1.5.0_10/bin/java -Djava.endorsed.dirs=/data/apps/jboss-4.0.3SP1/lib/endorsed -Dprogram.name=twiddle.sh -classpath /data/apps/jboss-4.0.3SP1/bin/twiddle.jar:/data/apps/jboss-4.0.3SP1/client/jbossall-client.jar:/data/apps/jboss-4.0.3SP1/client/getopt.jar:/data/apps/jboss-4.0.3SP1/client/log4j.jar:/data/apps/jboss-4.0.3SP1/lib/jboss-jmx.jar:/data/apps/jboss-4.0.3SP1/lib/dom4j.jar org.jboss.console.twiddle.Twiddle -s 3.122.100.14:1099 serverinfo -l jboss.management.local:ServiceModule=jboss-service.xml,name=jboss%3aservice%3dinvoker%2ctype%3djrmp,J2EEServer=Local,J2EEApplication=null,j2eeType=MBean jboss.jca:service=CachedConnectionManager jboss.management.local:ServiceModule=jbossjca-service.xml,name=jboss.jca%3aservice%3dWorkManagerThreadPool,J2EEServer=Local,J2EEApplication=null,j2eeType=MBean jboss.management.local:ServiceModule=jmx-invoker-service.xml,name=jboss.jmx%3atype%3dadaptor%2cname%3dInvoker%2cprotocol%3djrmp%2cservice%3dproxyFactory,J2EEServer=Local,J2EEApplication=null,j2eeType=MBean ... (truncated the output, you get the idea returns a full Mbean list for an instance on the box listening on an entirely different IP). If I run the exact same command several times in a row, it will connect to different instances each time - the ".14" IP isn't plumbed on the box at all, it however returns data from the instances listening on .23, .24, .153, etc (we have about 10 instances running). -- 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