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-tp1462p1470.html

Could you open run_monitor.sh and fix the following line to have -Dcom.sun.management.jmxremote.authenticate=false and run it again?

java -server -cp "lib/*" -Dcom.sun.management.jmxremote.authenticate=false org.ngrinder.NGrinderAgentStarter --mode monitor --command run $@

2014-04-08 12:17 GMT+09:00 Juno Yoon <[hidden email]>:

Thanks for your feedback.

Yes. We already tested this before and I saw it worked before.

I have a question to you. Do your target have the multiple IPs?

2014-04-08 2:34 GMT+09:00 John Warner [via ngrinder] <[hidden email]>:

Hi,

Thanks for getting back to me. Yeah, I saw about the timeout, which is why I grabbed the source (3.3.1) and built everything myself with a much bigger timeout.

But that still didn't resolve the issue. It's almost like the RMI request isn't being handled correctly. It makes it into the RMI lookup but fails silently at that point. Unfortunately that's in code which I can't view in a debugger, so I can't see what it's up to.

It works when everything is on the same machine, but I see it takes a different approach to talking to the monitor at that point, so that makes sense. Have you seen it working remotely?

--
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-tp1462p1464.html

To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML