DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41028>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41028 Summary: JMeter distributed testing doesn't alert the user when the jmeter-server is unreachable Product: JMeter Version: 2.2.1 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: Main AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Due to Sun bug 4665037 (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665037) rmi in linux may not work if the name resolution is not properly configured. The problem is that under linux the jmeter server in rmi will be bound to ip 127.0.0.1 instead of the real (externally reachable) ip address of the machine. So although the jmeter master will be able to locate the "JMeterEngine" instances via the RMI registry. It will not be able to connect to the actual instances. Actually JMeter will not complain when this happens it doesn't tell you anything when launching jmeter-server ( not even in logs) and it will silently fail when trying to start the remote instances (no trace in the logs). It's very easy to include a check in RemoteJMeterEngineImpl.java to check InetAddress.getLocalHost().isLoopbackAddress() and raise an exception or at least log it. Also it would be very convenient to add log statements in the catch java.rmi.xxxxException blocks in the ClientJMeterEngine.java. } catch (java.rmi.ConnectException e) { log.error("rmi exception", e); because otherwise this kind of failures go unnoticed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
