Re: Unable to get monitoring working in latest ngrinder

Posted by junoyoon on
URL: http://ngrinder.373.s1.nabble.com/Unable-to-get-monitoring-working-in-latest-ngrinder-tp1462p1463.html

Currently, there is 1 second timeout logic when connecting monitor from controller not to be blocked in the monitor connection phase.
We observed it cause some problem when the target server is under stress. It delays connections and finally make the monitor connection failed.
We take this as a serious bug, we'll fix this in 3.3.1 soon. 
P.S We didn't release 3.3.1 yet. :-)


2014-04-07 22:15 GMT+09:00 John Warner [via ngrinder] <[hidden email]>:
Hello,

We've been struggling to get the monitor working with the latest version of ngrinder (3.3.1) and were wondering if you had any ideas.

It looks like the controller cannot communicate with the monitor's JMX bean over RMI, which is something I've confirmed by trying to connect using jmc. We've been all over the network settings and all ports are open, nothing is locked down and I've even tried it on an entirely separate network and on an internal network using VMWare and still it doesn't work.

I can see that the initial connection does make it through as I turned on logging within the monitor and I get this line output:

FINER: RMI TCP Connection(3)-10.43.196.192: [10.43.196.192: sun.rmi.registry.RegistryImpl[0:0:0, 0]: java.rmi.Remote lookup(java.lang.String)]

10.43.196.192 is the IP address of the machine making the request, so it's definitely getting through, but then nothing happens and the request just hangs.

We've tried this with both Java 7 and Java 6 without any luck. The problem seems to be that it's disappearing into the RMI lookup method but I can't work out why.

Any ideas?

--
John Warner


If you reply to this email, your message will be added to the discussion below:
http://ngrinder.642.n7.nabble.com/Unable-to-get-monitoring-working-in-latest-ngrinder-tp1462.html
To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML