Re: Grinder Error
Amit Kumar <[email protected]>
| Newsgroups | gmane.comp.java.grinder.user |
|---|---|
| Message-ID | <CAORqQS4Ge+ymBAJuPzJvz=712VE7oPK4JpoJD2yN0bcNte-sfQ@mail.gmail.com> |
Thanks for prompt reply !!! Following are the configuration that I'm using OS-- Windows 7 Java version --- java version "1.6.0_16" Java(TM) SE Runtime Environment (build 1.6.0_16-b01) Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing) Firefox version ---- 26.0 Grinder version ----3.11 I simply go to google.com site to record test case but still getting ssl exception. I have started the tcpproxy with ssl debugging as suggested by you. I have attached output file. Kindly suggest some solution to resolve this problem. Regards, Amit Kumar On Mon, May 5, 2014 at 8:40 PM, Philip Aston <[email protected]> wrote: > Definitely unexpected - possibly a mismatch between the available > protocols in Java and the server. What version of Java are you using (java > -version)? > > You might get hints if you enable Java's SSL debugging. You can do this > by starting the TCPProxy with java *-Djavax.net.debug=ssl*net.grinder.TCPProxy-console -http > > FWIW, I found I couldn't convince FireFox 29 to allow me to add an > exception for Google+. I guess defaults are being made harder to override - > post-Heartbleed paranoia and all that. OTOH, other sites were fine. > > - Phil > > > > > On 05/05/14 15:31, Amit Kumar wrote: > > Hi, > > I'm new to grinder tool. I'm able to start console, agent and tcpproxy > with following command > > java net.grinder.TCPProxy -console -http > myscript.py > > I configured firefox for proxy settings as well. > > But whenever I opened any url in firefox, I'm getting following error on > TCPProxy console. > > Kindly suggest how I can resolve this error > > > 19:51:47.699 [Filter thread for plus.google.com:443->127.0.0.1:51738] > ERROR: jav > > a.lang.IllegalStateException: Internal error > > javax.net.ssl.SSLException: java.lang.IllegalStateException: Internal error > > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown > Source) ~ > > [na:1.6] > > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown > Source) ~[na > > :1.6] > > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown > Source) ~[na > > :1.6] > > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(Unknown So > > urce) ~[na:1.6] > > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(Unknown So > > urce) ~[na:1.6] > > at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown > Source) ~[na > > :1.6] > > at > net.grinder.tools.tcpproxy.AbstractTCPProxyEngine$FilteredStreamThrea > > d.interruptibleRun(AbstractTCPProxyEngine.java:431) > ~[grinder-http-3.10.jar:na] > > at > net.grinder.util.thread.InterruptibleRunnableAdapter.run(Interruptibl > > eRunnableAdapter.java:58) [grinder-core-3.10.jar:na] > > at java.lang.Thread.run(Unknown Source) [na:1.6.0_24] > > Caused by: java.lang.IllegalStateException: Internal error > > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.initHandshaker(Unknown Sou > > rce) ~[na:1.6] > > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown > Source) > > ~[na:1.6] > > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un > > known Source) ~[na:1.6] > > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown Sou > > rce) ~[na:1.6] > > ... 4 common frames omitted > > 19:51:52.991 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > > 19:51:58.018 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > > 19:52:03.021 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > > 19:52:08.023 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > > 19:52:13.025 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > > 19:52:18.400 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > > 19:52:23.403 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > > 19:53:19.591 [main] ERROR: Failed to determine proxy destination. > > Client opened connection but sent no bytes. > > -- > Regards, > Amit Kumar > > > > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find > out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > grinder-use mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/grinder-use > > -- Regards, Amit Kumar ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ grinder-use mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/grinder-use
myscript.py
(text/plain, 410.8 KB) - not displayed