You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2004/01/19 13:19:07 UTC

DO NOT REPLY [Bug 23487] - Remote execution from command-line does not work correctly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23487>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23487

Remote execution from command-line does not work correctly





------- Additional Comments From dirk.temme@hoogehuys.nl  2004-01-19 12:19 -------
In org.apache.jmeter.engine.ClientJMeterEngine.run() I have put an extra try-
catch block:

        try {
            theTree.traverse(sampleListeners);
        }
        catch (java.lang.IndexOutOfBoundsException e) {
            System.out.println("A java.lang.IndexOutOfBoundsException appeared."
                                + "\nApparently the Listener is already 
replaced."
                                + "\nTry to move on...");
        }

That seems to work. The problem was that in the HashTree corresponding to the 
testplan, for remote testing, any ResultCollector has to be replaced bij a 
RemoteListenerWrapper. This replacement was done bij all instances of 
ClientJMeterEngine (one per remote testPC). Only the first of these instances 
succeeded in doing this. The idea behind above workaround is that once the 
replacement is done, all is OK, and the other ClientJMeterEngine's don't have 
to bother.

This workaround is not THE solution, it seems to me. The code for replacing the 
ResultCollector should be somewhere else probably.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org