6 Replies Latest reply on Aug 25, 2006 2:06 AM by dheeraj7400

Error while trying to get no. of threads using twiddle.bat

dheeraj7400 Aug 23, 2006 8:18 AM

I'm fairly new to JBoss and I was trying to figure out how to use twiddle. I did not find a lot of documentation or examples posted and for some reason I could not get it through my fat head.

i just want to the thread count of the server running on localhost:8877
and getting following error

can any body have any idea what i m missing...

thanks
dheeraj

D:\jboss-3.2.5\bin>twiddle.bat -s localhost:8877 serverinfo -c
17:36:49,764 WARN [NamingContext] Failed to connect to localhost:8877
javax.naming.CommunicationException: Failed to retrieve stub from server localhost:8877 [Root exception is java.io.EOFException]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:207)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1185)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:239)
at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:257)
at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:51)
at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:128)
at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:47)
at org.jboss.console.twiddle.command.ServerInfoCommand.execute(ServerInfoCommand.java:118)
at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:288)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2165)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2631)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:734)
at java.io.ObjectInputStream.(ObjectInputStream.java:253)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:194)
... 11 more
17:36:54,780 ERROR [Twiddle] Exec failed
org.jboss.util.NestedRuntimeException: Receive timed out; - nested throwable: (javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed
out])
at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:132)
at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:47)
at org.jboss.console.twiddle.command.ServerInfoCommand.execute(ServerInfoCommand.java:118)
at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:288)
Caused by: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1119)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1196)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:239)
at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:257)
at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:51)
at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:128)
... 3 more
Caused by: java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:711)
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1089)
... 11 more

1. Re: Error while trying to get no. of threads using twiddle.b

peterj Aug 23, 2006 10:54 AM (in response to dheeraj7400)

Twiddle documentation is at http://docs.jboss.org/jbossas/jboss4guide/r2/html/ch2.chapter.html, about a third of the way down the page.

Why are you using port 8877? Did you change the JNDI port for JBoss? Usually it is 1099, in which case you don't have to provide it.
Actions
2. Re: Error while trying to get no. of threads using twiddle.b

dheeraj7400 Aug 23, 2006 11:23 AM (in response to dheeraj7400)

Thanks for replay,

i have my application deployed on port 8877 of jboss...
and for port 1099 port also show the same error
Actions
3. Re: Error while trying to get no. of threads using twiddle.b

peterj Aug 23, 2006 11:40 AM (in response to dheeraj7400)

i have my application deployed on port 8877 of jboss...

Do you mean that you changed the http port? In other words, you accessy our app via http://localhost:8877/xxx?

No never said if you also changed the JNDI port. With JBoss running, run "netstat -a -b" at a command line and let me know all of the ports used by java.exe. Or if you have tcpview, use that instead, in which case you can copy and paste the data from tcpview into your reply.
Actions
4. Re: Error while trying to get no. of threads using twiddle.b

dheeraj7400 Aug 24, 2006 2:48 AM (in response to dheeraj7400)

Thanks Peter,

It's working now ....

dheeraj
Actions
5. Re: Error while trying to get no. of threads using twiddle.b

peterj Aug 24, 2006 10:39 AM (in response to dheeraj7400)

For the benefit of others, could you post what you changed that caused it to start working?
Actions
6. Re: Error while trying to get no. of threads using twiddle.b

dheeraj7400 Aug 25, 2006 2:06 AM (in response to dheeraj7400)

Sure,

i m running two intance of jboss in same m/c having diffrent port setting one for my application and another for my logger ,in my case the jndi port is 3198 and this is the root cause.

dheeraj
Actions

Go to original post