[Grinder-use] TCPProxy crashed now for no reason

[David L. W. <dw...@ya...>]

Hello:
I am sending this message in for Vincent Taso.

We were testing fine, now Grinder3 beta18 just exited for no reason.

Thank You
David L. Wasler

--- Vincent Tsao <vin...@ya...> wrote:
 I'm doing load testing on a WebLogic server. Tried to use Grinder3.0
 beta 18's TCPProxy (on Windows XP) to capture test scripts. It worked
fine for a few days. But now the TCPProxy could stop at any time. No
error messages but
 "Engine exited." Has anyone had the same experience? Possible causes
 that you may think of? 
 
Thanks a lot, Vincent
 
 DOS commands and responses:
"D:\grinder3.18\tests>cd D:\grinder3.18\tests
 D:\grinder3.18\tests>set
 CLASSPATH=D:\grinder3.18\lib\grinder.jar;%CLASSPATH%
D:\grinder3.18\tests>set PATH=D:\Sun\AppServer\jdk\bin;%PATH%
 D:\grinder3.18\tests>java net.grinder.TCPProxy -httpPlugin -ssl
 -keyStore
 test.k
 eystore -keyStorePassword myhealthevet -timeout 180
 Script will be generated to the files 'httpscript.py' and
 'httpscript_tests.py'
Initialising as an HTTP/HTTPS proxy with the parameters:
    Request filters:    HTTPPluginTCPProxyFilter
   Response filters:   HTTPPluginTCPProxyResponseFilter
   Local host:         localhost
    Local port:         8001
    Key store:          test.keystore
    Key store password: ************
Engine initialised, listening on port 8001
 Engine exited"