[jboss-jira] [JBoss JIRA] Commented: (JBAS-5157) Twiddle to bad host/port returns data!
Peter Hufnagel (JIRA)
jira-events at lists.jboss.org
Sat Jan 19 16:53:36 EST 2008
[ http://jira.jboss.com/jira/browse/JBAS-5157?page=comments#action_12395853 ]
Peter Hufnagel commented on JBAS-5157:
--------------------------------------
Additional info:
[bb4 at cipcrpdwas01 ext]$ telnet localhost 1099
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host: Connection refused
[phufnag at cipcrpdwas01 ext]$
[phufnag at cipcrpdwas01 ext]$ /sbin/ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:11:0A:58:E8:82
inet addr:3.122.100.229 Bcast:3.122.103.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:366486019 errors:0 dropped:0 overruns:0 frame:0
TX packets:686912807 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:711342958 (678.3 Mb) TX bytes:1767426723 (1685.5 Mb)
Base address:0x4000 Memory:f05e0000-f0600000
[phufnag at cipcrpdwas01 ext]$ telnet 3.122.100.229 1099
Trying 3.122.100.229...
telnet: connect to address 3.122.100.229: Connection refused
telnet: Unable to connect to remote host: Connection refused
>> Neither "localhost" (loopback) or the base IP of the box have port 1099 active...
[phufnag at cipcrpdwas01 ext]$ /data/apps/jdk1.5.0_10/bin/java -Djava.endorsed.dirs=/data/apps/jboss-4.2.1.GA/lib/endorsed -Dprogram.name=twiddle.sh -classpath /data/apps/jboss-4.2.1.GA/bin/twiddle.jar:/data/apps/jboss-4.2.1.GA/client/jbossall-client.jar:/data/apps/jboss-4.2.1.GA/client/getopt.jar:/data/apps/jboss-4.2.1.GA/client/log4j.jar:/data/apps/jboss-4.2.1.GA/lib/jboss-jmx.jar:/data/apps/jboss-4.2.1.GA/lib/dom4j.jar org.jboss.console.twiddle.Twiddle --server 3.122.100.229:1099 serverinfo -l
jboss.management.local:ServiceModule=jboss-service.xml,name=jboss%3aservice%3dinvoker%2ctype%3djrmp,J2EEServer=Local,J2EEApplication=null,j2eeType=MBean
jboss.management.local:ServiceModule=farm-service.xml,name=jboss%3aservice%3dFarmMember%2cpartition%3dGAPCHealthcareCluster,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 it again), Yet rather than complaining that it can't reach the IP in question, it connects to, uh, *some* jboss instance on the box (one of many).
>> Reproducable on both 4.0.3 (the prior one) and 4.2.1 (I have 4.2.2 and could try it there).
> 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.0.4RC1, JBossAS-4.2.1.GA
> 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 at 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 at 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
More information about the jboss-jira
mailing list