JBoss twiddle extraordinarily slow
843793Feb 9 2010 — edited Mar 3 2010I just recently discovered JBoss twiddle (twiddle appears to be the command line equivalent of jmx-console)..
I have environments with 3 or 4 JBoss servers.
As I have several JBoss servers, I have changed ports - one server in each environment remains configured with jboss:service=Naming listening on the default port 1099.
I have these environments running on Windows,
I also have these environments running on CentOS.
On both platforms jmx-console works a charm.
On Windows twiddle works fine,
on CentOS twiddle takes around 3 minutes for anything
(except help which is instant as it does not need the server),
but it does eventually complete.
Looking at the source for twiddle and the log it seems twiddle is stuck in a call to getMBeanServer().
Several Google hits suggest I have messed up DNS
but I am just using a hosts file and everything else works including java.net.InetAddress.getByName().
Does anyone have any idea what is missing
or what I can do to find out what it is doing for 3 minutes?
If this is not some known issue I guess I will find the source
and run it in eclipse in debug mode - I suspect I will end up in some native code
but maybe I will still know more.