Login | Register
My pages Projects Community openCollabNet

Discussions > users > [maxq-users] Connection reset by peer

maxq
Discussion topic

Hide all messages in topic

All messages in topic

Re: [maxq-users] Connection reset by peer

Author oliverbock
Full name Oliver Bock
Date 2004-10-18 15:55:36 PDT
Message On 19/10/2004, at 03:58, Stephen Rufle wrote:
> New error
> INFO: browser stopped listening: Connection reset by peer: socket
> write error
> java.io.IOException: unterminated line in request header
> at
> com.bitmechanic.maxq​.HttpRequestHeader.r​eadLine(HttpRequestH​eader.java:
> 189)
> at
> com.bitmechanic.maxq​.HttpRequestHeader.​<init>(HttpRequ​estHeader.java:
> 106)
> at
> com.bitmechanic.maxq​.RequestHandler.init​ClientServerConnecti​ons(Request
> Handler.java:42)
> at com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​138)
> at java.lang.Thread.run(Unknown Source)
> Oct 18, 2004 10:50:01 AM com.bitmechanic.maxq​.RequestHandler run

You've been very patient. Hopefully this is now fixed too.

> I also had to changed line 237 and 248 the server socket was null at
> some point. I suspect that these issues are specific to IE , since in
> previous posts you do not get these problems using a superior broswer
> like Safari :)...

I have adopted your null check while closing the serverSocket because
it may indeed be null if an exception occurs before it is opened.
However I cannot see how clientSocket could ever be null so I have
added an assert to detect that case earlier. Strangely, when I tested
this on IE it started hanging after the first request. I'm not sure
what this is about, but I do not have time to fix it. I suspect that
it was not caused by this most recent fix, but by something from
before. Does it work for you?

I've committed these changes to CVS.


   Oliver


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

Re: [maxq-users] Connection reset by peer

Author Stephen Rufle <srufle at salmonllc dot com>
Full name Stephen Rufle <srufle at salmonllc dot com>
Date 2004-10-18 10:58:08 PDT
Message New error
INFO: browser stopped listening: Connection reset by peer: socket write
error
java.io.IOException: unterminated line in request header
    at
com.bitmechanic.maxq​.HttpRequestHeader.r​eadLine(HttpRequestH​eader.java:189)
    at
com.bitmechanic.maxq​.HttpRequestHeader.​<init>(HttpRequ​estHeader.java:106)
    at
com.bitmechanic.maxq​.RequestHandler.init​ClientServerConnecti​ons(RequestHandler.j​ava:42)
    at com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​138)
    at java.lang.Thread.run(Unknown Source)
Oct 18, 2004 10:50:01 AM com.bitmechanic.maxq​.RequestHandler run

I also had to changed line 237 and 248 the server socket was null at
some point. I suspect that these issues are specific to IE , since in
previous posts you do not get these problems using a superior broswer
like Safari :)
// We used not to close serverSocket. A comment said:
                // //the server should close its socket
                // //automatically
                // However they did not _appear_ to be closing, and this
does
                // not surprise me because we are probably passing
Keep-Alive
                // headers through to the server. oliverbock
               
               
                if ( serverSocket != null)
                {
                serverSocket.close();
                log.trace("closed server socket");
                }
                else
                {
                     log.trace("serverSocket was null");
                }
       
                //close the client connection
                if ( clientSocket != null)
                {
                clientSocket.close();
                log.trace("closed client socket");
                }
                else
                {
                     log.trace("clientSocket was null");
                }

> On 15/10/2004, at 14:43, Stephen Rufle wrote:
>
>> OK that made it better I still got an exception
>>
>> I fixed by adding...
>
>
> You only needed to make that change because I did not properly abort
> the request when I changed MaxQ this morning. I've fixed that now so
> if you update your code from CVS you should be able to remove your fix.
>
>> goto http://www.fujifilm.​com/JSP/fuji/epartne​rs/index.jsp
>> there are some dropdown menus open a new browser after starting to
>> record a compact script (probably does not matter compact or
>> standard) and rollover the flyout , do it enough and you should get
>> "Connection reset" error box in GUI and the following stack trace
>>
>> INFO: browser stopped listing: Connection reset by peer: socket
>> write error
>> java.net.SocketException: Connection reset
>> at java.net.SocketInput​Stream.read(Unknown Source)
>> at sun.nio.cs.StreamDec​oder$CharsetSD.read​Bytes(Unknown
>> Source)
>> at sun.nio.cs.StreamDec​oder$CharsetSD.impl​Read(Unknown Source)
>> at sun.nio.cs.StreamDec​oder.read(Unknown Source)
>> at java.io.InputStreamR​eader.read(Unknown Source)
>> at java.io.BufferedRead​er.fill(Unknown Source)
>> at java.io.BufferedRead​er.readLine(Unknown Source)
>> at java.io.BufferedRead​er.readLine(Unknown Source)
>> at
>> com.bitmechanic.maxq​.HttpRequestHeader.​<init>(HttpRequ​estHeader.java:
>> 76)
>> at
>> com.bitmechanic.maxq​.RequestHandler.init​ClientServerConnecti​ons(Request
>> Handler.java:48)
>> at
>> com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​136)
>> at java.lang.Thread.run(Unknown Source)
>> Oct 14, 2004 9:33:58 PM com.bitmechanic.maxq​.RequestHandler run
>> INFO: browser stopped listing: Connection reset by peer: socket
>> write error
>
>
> This stack trace shows an error at HttpRequestHeader.java line 76,
> which is a comment in the version of that file that is in CVS. Are
> you using the version from CVS?
>
> I cannot reproduce your error here because my browser (Safari on Mac
> OS X) produces no HTTP requests for these rollovers. However it
> looks like your browser is aborting the request half-way through
> writing the headers to MaxQ. I suppose that this is a reasonable
> thing to do if the browser decides it no longer wants the page so I
> have changed MaxQ to be similarly quiet in these situations. Please
> tell me if it helps.
>
>
> Oliver
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
>


--
Stephen P Rufle
srufle at salmonllc dot com
H:480-802-7173
Yahoo IM: stephen_rufle
AOL IM: stephen0rufle


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

Re: [maxq-users] Connection reset by peer

Author oliverbock
Full name Oliver Bock
Date 2004-10-14 22:28:46 PDT
Message On 15/10/2004, at 14:43, Stephen Rufle wrote:
> OK that made it better I still got an exception
>
> I fixed by adding...

You only needed to make that change because I did not properly abort
the request when I changed MaxQ this morning. I've fixed that now so
if you update your code from CVS you should be able to remove your fix.

> goto http://www.fujifilm.​com/JSP/fuji/epartne​rs/index.jsp
>  there are some dropdown menus open a new browser after starting to
> record a compact script (probably does not matter compact or standard)
> and rollover the flyout , do it enough and you should get "Connection
> reset" error box in GUI and the following stack trace
>
> INFO: browser stopped listing: Connection reset by peer: socket write
> error
> java.net.SocketException: Connection reset
>         at java.net.SocketInput​Stream.read(Unknown Source)
>         at sun.nio.cs.StreamDec​oder$CharsetSD.read​Bytes(Unknown
> Source)
>         at sun.nio.cs.StreamDec​oder$CharsetSD.impl​Read(Unknown Source)
>         at sun.nio.cs.StreamDec​oder.read(Unknown Source)
>         at java.io.InputStreamR​eader.read(Unknown Source)
>         at java.io.BufferedRead​er.fill(Unknown Source)
>         at java.io.BufferedRead​er.readLine(Unknown Source)
>         at java.io.BufferedRead​er.readLine(Unknown Source)
>         at
> com.bitmechanic.maxq​.HttpRequestHeader.​<init>(HttpRequ​estHeader.java:
> 76)
>         at
> com.bitmechanic.maxq​.RequestHandler.init​ClientServerConnecti​ons(Request
> Handler.java:48)
>         at
> com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​136)
>         at java.lang.Thread.run(Unknown Source)
> Oct 14, 2004 9:33:58 PM com.bitmechanic.maxq​.RequestHandler run
> INFO: browser stopped listing: Connection reset by peer: socket write
> error

This stack trace shows an error at HttpRequestHeader.java line 76,
which is a comment in the version of that file that is in CVS. Are you
using the version from CVS?

I cannot reproduce your error here because my browser (Safari on Mac OS
X) produces no HTTP requests for these rollovers. However it looks
like your browser is aborting the request half-way through writing the
headers to MaxQ. I suppose that this is a reasonable thing to do if
the browser decides it no longer wants the page so I have changed MaxQ
to be similarly quiet in these situations. Please tell me if it helps.


    Oliver


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

Re: [maxq-users] Connection reset by peer

Author fcohen
Full name Frank Cohen
Date 2004-10-14 21:49:25 PDT
Message Cool. Glad to help. -Frank


On Oct 14, 2004, at 9:31 PM, Oliver Bock wrote:

> Hi Frank,
>
> That would be a big improvement. Please do also add it to MaxQ.
>
> Although it may not appear so at first glance, MaxQ handles errors
> better than it used to. In particular:
>
> - It used to throw away exceptions that occurred in the RequestHandler
> and ProxyServer threads. These are now sent to the GUI for display.
>
> - If an error is exclusively in Jython then you will just see the
> Python stack trace, which is generally short and readable.
>
> - Most other exceptions are allowed to percolate up except where there
> is a good case for either:
> - Turning them into a more readable form (Utils.UserException), or
> - explicitly ignoring them in just the area that they occur. (with
> comments)
>
>
> Oliver
>
> --
> On 15/10/2004, at 14:23, Frank Cohen wrote:
>> Hi Oliver: Expect a bunch of patches from me on the way MaxQ handles
>> errors. One change I already made to TestMaker when the proxy gets an
>> error from the host is to reply to the browser with an error page.
>> You can take them or leave them for MaxQ but they are definitely
>> going into TM. :-)
>>
>> -Frank
>>
>>
>> On Oct 14, 2004, at 5:02 PM, Oliver Bock wrote:
>>
>>> Stephen,
>>>
>>> I have changed MaxQ so that it is less noisy when it cannot write a
>>> response back to the browser. (It will still print a complaint to
>>> the DOS window, but it should not show a dialog nor print a stack
>>> trace.)
>>>
>>> Can you please get MaxQ using CVS and try that? This is the only
>>> change in CVS since v0.97.
>>>
>>>
>>> Oliver
>>>
>>> --
>>> On 15/10/2004, at 09:54, Stephen Rufle wrote:
>>>
>>>> Here is  stack trace , I turned on the -d parm for you :)
>>>>
>>>> This is what I think is happening  "but it also happens implicitly
>>>> if a user clicks on another link before the current page has
>>>> finished loading everything"
>>>>
>>>>
>>>> I get a "Broken pipe" message when the user cancels an operation on
>>>> the web browser.  This happens when the user clicks cancel, but it
>>>> also happens implicitly if a user clicks on another link before the
>>>> current page has finished loading everything.  I'm adding a fix to
>>>> suppress this error now.
>>>>
>>>> However your error may be different since you are getting
>>>> "Connection reset by peer", so perhaps yours is a different
>>>> situation.  You should see a Java stack trace in your DOS window
>>>> when this box appears.  Could you please reply with that?
>>>>
>>>>
>>>>    Oliver
>>>>
>>>> --
>>>> On 15/10/2004, at 04:10, Stephen Rufle wrote:
>>>>
>>>>
>>>> Is there a way for maxq to suppress the showing of the "MaxQ
>>>> Error" box when a  socket write error happens. It is confusing my
>>>> tester , she is new to using the tool and is never sure that she
>>>> actually recorded the url that got the socket write error. I
>>>> watched her and it seems that the socket write error is
>>>> meaningless.
>>>>
>>>> Is there a switch that needs flipping :)
>>>>
>>>> -- 
>>>> Stephen P Rufle
>>>> srufle at salmonllc dot com
>>>> H:480-802-7173
>>>> Yahoo IM: stephen_rufle
>>>> AOL IM: stephen0rufle
>>>>
>>>>
>>>>
>>>> --------------------​--------------------​--------------------​--------
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>>>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --------------------​--------------------​--------------------​--------
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>>>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -- Stephen P Rufle
>>>> srufle at salmonllc dot com
>>>> H:480-802-7173
>>>> Yahoo IM: stephen_rufle
>>>> AOL IM: stephen0rufle
>>>> Microsoft Windows 2000 [Version 5.00.2195]
>>>> (C) Copyright 1985-2000 Microsoft Corp.
>>>>
>>>> C:\Documents and Settings\srufle>maxq
>>>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>>>> INFO: MaxQ Proxy Recorder v0.97
>>>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>>>> INFO: Proxy server started on port: 8090
>>>> C:\Documents and Settings\srufle>maxq -d
>>>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>>>> INFO: MaxQ Proxy Recorder v0.97
>>>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>>>> INFO: Proxy server started on port: 8090
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.ProxyServer run
>>>> FINEST: New connection. Creating new RequestHandler thread.
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: read request header
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: wrote request header
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: no request body
>>>> Oct 14, 2004 4:46:59 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>>> FINE: recording url:
>>>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq.Utils getParams
>>>> FINE: parsing: folderID=695
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed request
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 1329 bytes
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 609 bytes
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 8192 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 2392 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 1003 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 952 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 960 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 990 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 785 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: transferred response
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseResponseCode
>>>> FINE: HTTP response code: 200
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: content-type: text/html
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed response
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed server socket
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed client socket
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>>>> FINEST: New connection. Creating new RequestHandler thread.
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: read request header
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: wrote request header
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: no request body
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>>> FINE: recording url:
>>>> http://maxq.tigris.o​rg/branding/images/
>>>> icon_arrowfolderopen2_sml.gif
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed request
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>>>> FINEST: New connection. Creating new RequestHandler thread.
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 238 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: transferred response
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseResponseCode
>>>> FINE: HTTP response code: 304
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: No content-type header! First few lines:
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: http/1.1 304 not modified
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>>>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: connection: close
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: etag: "7486c7-298-c5488f40"
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> processResponse
>>>> FINE: Ignoring response because content type is not known: null
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed response
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed server socket
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed client socket
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>>>> FINEST: New connection. Creating new RequestHandler thread.
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: read request header
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: wrote request header
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: no request body
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>>> FINE: recording url:
>>>> http://maxq.tigris.o​rg/branding/images/
>>>> icon_arrowfolderclosed1_sml.gif
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed request
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: read request header
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: wrote request header
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: no request body
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 238 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: transferred response
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseResponseCode
>>>> FINE: HTTP response code: 304
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: No content-type header! First few lines:
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: http/1.1 304 not modified
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>>>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: connection: close
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: etag: "7486c3-1b9-c5488f40"
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> processResponse
>>>> FINE: Ignoring response because content type is not known: null
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed response
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>>> FINE: recording url:
>>>> http://maxq.tigris.o​rg/branding/images/i​con_doc_sml.gif
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed request
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed server socket
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed client socket
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 238 bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: transferred response
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseResponseCode
>>>> FINE: HTTP response code: 304
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: No content-type header! First few lines:
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: http/1.1 304 not modified
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>>>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: connection: close
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: etag: "7486cd-163-c5488f40"
>>>> Oct 14, 2004 4:47:00 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> processResponse
>>>> FINE: Ignoring response because content type is not known: null
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed response
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed server socket
>>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed client socket
>>>> Oct 14, 2004 4:47:01 PM com.bitmechanic.maxq​.ProxyServer run
>>>> FINEST: New connection. Creating new RequestHandler thread.
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: read request header
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: wrote request header
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: no request body
>>>> Oct 14, 2004 4:47:02 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>>> FINE: recording url:
>>>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq.Utils getParams
>>>> FINE: parsing: folderID=695
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed request
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.ProxyServer run
>>>> FINEST: New connection. Creating new RequestHandler thread.
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: read request header
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: wrote request header
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: no request body
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 1329 bytes
>>>> java.net.SocketException: Connection reset by peer: socket write
>>>> error
>>>> at java.net.SocketOutpu​tStream.socketWrite0​(Native Method)
>>>> at java.net.SocketOutpu​tStream.socketWrite(​Unknown Source)
>>>> at java.net.SocketOutpu​tStream.write(Unknow​n Source)
>>>> at
>>>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandle
>>>> r.java:216)
>>>> at
>>>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandle
>>>> r.java:204)
>>>> at
>>>> com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​176)
>>>> at java.lang.Thread.run(Unknown Source)
>>>> Oct 14, 2004 4:47:02 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>>> FINE: recording url: http://maxq.tigris.o​rg/docs/install.html​
>>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed request
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 1268 bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 1024 bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 8192 bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: read 2763 bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: wrote bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>>> moveAvailableBytes
>>>> FINEST: buffered bytes
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: transferred response
>>>> Oct 14, 2004 4:47:04 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseResponseCode
>>>> FINE: HTTP response code: 200
>>>> Oct 14, 2004 4:47:04 PM
>>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>>> parseContentType
>>>> FINE: content-type: text/html
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: processed response
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed server socket
>>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>>> FINEST: closed client socket
>>>>
>>>> --------------------​--------------------​--------------------​--------
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>>>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>>
>>>
>> ---
>> Frank Cohen, PushToTest, http://www.PushToTest.com, phone: 408 374
>> 7426
>> Author of "Java Testing and Design: From Unit Tests to Automated Web
>> Tests"
>> from Prentice Hall, details at http://thebook.pushtotest.com
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
---
Frank Cohen, PushToTest, http://www.PushToTest.com, phone: 408 374 7426
Author of "Java Testing and Design: From Unit Tests to Automated Web
Tests"
from Prentice Hall, details at http://thebook.pushtotest.com


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

Re: [maxq-users] Connection reset by peer

Author Stephen Rufle <srufle at salmonllc dot com>
Full name Stephen Rufle <srufle at salmonllc dot com>
Date 2004-10-14 21:43:25 PDT
Message *OK that made it better I still got an exception

I fixed by adding

      /*
         * Read by lines
         */
72 BufferedReader lines = new BufferedReader(new
InputStreamReader(In));

74 if (lines != null)
75 {

to com.bitmechanic.maxq​.HttpRequestHeader , I think that fixed this error.
*Oct 14, 2004 9:06:24 PM com.bitmechanic.maxq​.RequestHandler run
INFO: browser stopped listing: Connection reset by peer: socket write error
java.lang.NullPointerException
        at java.util.StringToke​nizer.<init>(U​nknown Source)
        at java.util.StringToke​nizer.<init>(U​nknown Source)
        at
com.bitmechanic.maxq​.HttpRequestHeader.​<init>(HttpRequ​estHeader.java:103)
        at
com.bitmechanic.maxq​.RequestHandler.init​ClientServerConnecti​ons(RequestHandler.j​ava:48)
        at com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​136)
        at java.lang.Thread.run(Unknown Source)
Oct 14, 2004 9:07:13 PM com.bitmechanic.maxq​.RequestHandler run
INFO: browser stopped listing: Connection reset by peer: socket write error

*goto http://www.fujifilm.​com/JSP/fuji/epartne​rs/index.jsp
 there are some dropdown menus open a new browser after starting to
record a compact script (probably does not matter compact or standard)
and rollover the flyout , do it enough and you should get "Connection
reset" error box in GUI and the following stack trace
*
INFO: browser stopped listing: Connection reset by peer: socket write error
java.net.SocketException: Connection reset
        at java.net.SocketInput​Stream.read(Unknown Source)
        at sun.nio.cs.StreamDec​oder$CharsetSD.read​Bytes(Unknown Source)
        at sun.nio.cs.StreamDec​oder$CharsetSD.impl​Read(Unknown Source)
        at sun.nio.cs.StreamDec​oder.read(Unknown Source)
        at java.io.InputStreamR​eader.read(Unknown Source)
        at java.io.BufferedRead​er.fill(Unknown Source)
        at java.io.BufferedRead​er.readLine(Unknown Source)
        at java.io.BufferedRead​er.readLine(Unknown Source)
        at
com.bitmechanic.maxq​.HttpRequestHeader.​<init>(HttpRequ​estHeader.java:76)
        at
com.bitmechanic.maxq​.RequestHandler.init​ClientServerConnecti​ons(RequestHandler.j​ava:48)
        at com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​136)
        at java.lang.Thread.run(Unknown Source)
Oct 14, 2004 9:33:58 PM com.bitmechanic.maxq​.RequestHandler run
INFO: browser stopped listing: Connection reset by peer: socket write error

Oliver Bock wrote:

> Stephen,
>
> I have changed MaxQ so that it is less noisy when it cannot write a
> response back to the browser. (It will still print a complaint to
> the DOS window, but it should not show a dialog nor print a stack
> trace.)
>
> Can you please get MaxQ using CVS and try that? This is the only
> change in CVS since v0.97.
>
>
> Oliver
>
> --
> On 15/10/2004, at 09:54, Stephen Rufle wrote:
>
>> Here is stack trace , I turned on the -d parm for you :)
>>
>> This is what I think is happening "but it also happens implicitly
>> if a user clicks on another link before the current page has
>> finished loading everything"
>>
>>
>> I get a "Broken pipe" message when the user cancels an operation on
>> the web browser. This happens when the user clicks cancel, but it
>> also happens implicitly if a user clicks on another link before the
>> current page has finished loading everything. I'm adding a fix to
>> suppress this error now.
>>
>> However your error may be different since you are getting
>> "Connection reset by peer", so perhaps yours is a different
>> situation. You should see a Java stack trace in your DOS window
>> when this box appears. Could you please reply with that?
>>
>>
>> Oliver
>>
>> --
>> On 15/10/2004, at 04:10, Stephen Rufle wrote:
>>
>>
>> Is there a way for maxq to suppress the showing of the "MaxQ Error"
>> box when a socket write error happens. It is confusing my tester ,
>> she is new to using the tool and is never sure that she actually
>> recorded the url that got the socket write error. I watched her and
>> it seems that the socket write error is meaningless.
>>
>> Is there a switch that needs flipping :)
>>
>> --
>> Stephen P Rufle
>> srufle at salmonllc dot com
>> H:480-802-7173
>> Yahoo IM: stephen_rufle
>> AOL IM: stephen0rufle
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>>
>>
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>>
>>
>>
>>
>>
>>
>> -- Stephen P Rufle
>> srufle at salmonllc dot com
>> H:480-802-7173
>> Yahoo IM: stephen_rufle
>> AOL IM: stephen0rufle
>> Microsoft Windows 2000 [Version 5.00.2195]
>> (C) Copyright 1985-2000 Microsoft Corp.
>>
>> C:\Documents and Settings\srufle>maxq
>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>> INFO: MaxQ Proxy Recorder v0.97
>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>> INFO: Proxy server started on port: 8090
>> C:\Documents and Settings\srufle>maxq -d
>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>> INFO: MaxQ Proxy Recorder v0.97
>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>> INFO: Proxy server started on port: 8090
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:46:59 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq.Utils getParams
>> FINE: parsing: folderID=695
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1329 bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 609 bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 8192 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 2392 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1003 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 952 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 960 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 990 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 785 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
>> FINE: HTTP response code: 200
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: content-type: text/html
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/branding/images/i​con_arrowfolderopen2​_sml.gif
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 238 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
>> FINE: HTTP response code: 304
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: No content-type header! First few lines:
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: http/1.1 304 not modified
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: connection: close
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: etag: "7486c7-298-c5488f40"
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>> FINE: Ignoring response because content type is not known: null
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/branding/images/i​con_arrowfolderclose​d1_sml.gif
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 238 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
>> FINE: HTTP response code: 304
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: No content-type header! First few lines:
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: http/1.1 304 not modified
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: connection: close
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: etag: "7486c3-1b9-c5488f40"
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>> FINE: Ignoring response because content type is not known: null
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/branding/images/i​con_doc_sml.gif
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 238 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
>> FINE: HTTP response code: 304
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: No content-type header! First few lines:
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: http/1.1 304 not modified
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: connection: close
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: etag: "7486cd-163-c5488f40"
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>> FINE: Ignoring response because content type is not known: null
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:01 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:02 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq.Utils getParams
>> FINE: parsing: folderID=695
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1329 bytes
>> java.net.SocketException: Connection reset by peer: socket write error
>> at java.net.SocketOutpu​tStream.socketWrite0​(Native Method)
>> at java.net.SocketOutpu​tStream.socketWrite(​Unknown Source)
>> at java.net.SocketOutpu​tStream.write(Unknow​n Source)
>> at
>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler.j
>> ava:216)
>> at
>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler.j
>> ava:204)
>> at
>> com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​176)
>> at java.lang.Thread.run(Unknown Source)
>> Oct 14, 2004 4:47:02 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url: http://maxq.tigris.o​rg/docs/install.html​
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1268 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1024 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 8192 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 2763 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:04 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
>> FINE: HTTP response code: 200
>> Oct 14, 2004 4:47:04 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: content-type: text/html
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
>


--
Stephen P Rufle
srufle at salmonllc dot com
H:480-802-7173
Yahoo IM: stephen_rufle
AOL IM: stephen0rufle
Attachments

Re: [maxq-users] Connection reset by peer

Author oliverbock
Full name Oliver Bock
Date 2004-10-14 21:31:14 PDT
Message Hi Frank,

That would be a big improvement. Please do also add it to MaxQ.

Although it may not appear so at first glance, MaxQ handles errors
better than it used to. In particular:

- It used to throw away exceptions that occurred in the RequestHandler
and ProxyServer threads. These are now sent to the GUI for display.

- If an error is exclusively in Jython then you will just see the
Python stack trace, which is generally short and readable.

- Most other exceptions are allowed to percolate up except where there
is a good case for either:
   - Turning them into a more readable form (Utils.UserException), or
   - explicitly ignoring them in just the area that they occur. (with
comments)


    Oliver

--
On 15/10/2004, at 14:23, Frank Cohen wrote:
> Hi Oliver: Expect a bunch of patches from me on the way MaxQ handles
> errors. One change I already made to TestMaker when the proxy gets an
> error from the host is to reply to the browser with an error page. You
> can take them or leave them for MaxQ but they are definitely going
> into TM. :-)
>
> -Frank
>
>
> On Oct 14, 2004, at 5:02 PM, Oliver Bock wrote:
>
>> Stephen,
>>
>> I have changed MaxQ so that it is less noisy when it cannot write a
>> response back to the browser. (It will still print a complaint to
>> the DOS window, but it should not show a dialog nor print a stack
>> trace.)
>>
>> Can you please get MaxQ using CVS and try that? This is the only
>> change in CVS since v0.97.
>>
>>
>> Oliver
>>
>> --
>> On 15/10/2004, at 09:54, Stephen Rufle wrote:
>>
>>> Here is  stack trace , I turned on the -d parm for you :)
>>>
>>> This is what I think is happening  "but it also happens implicitly
>>> if a user clicks on another link before the current page has
>>> finished loading everything"
>>>
>>>
>>> I get a "Broken pipe" message when the user cancels an operation on
>>> the web browser.  This happens when the user clicks cancel, but it
>>> also happens implicitly if a user clicks on another link before the
>>> current page has finished loading everything.  I'm adding a fix to
>>> suppress this error now.
>>>
>>> However your error may be different since you are getting
>>> "Connection reset by peer", so perhaps yours is a different
>>> situation.  You should see a Java stack trace in your DOS window
>>> when this box appears.  Could you please reply with that?
>>>
>>>
>>>    Oliver
>>>
>>> --
>>> On 15/10/2004, at 04:10, Stephen Rufle wrote:
>>>
>>>
>>> Is there a way for maxq to suppress the showing of the "MaxQ Error"
>>> box when a  socket write error happens. It is confusing my tester ,
>>> she is new to using the tool and is never sure that she actually
>>> recorded the url that got the socket write error. I watched her and
>>> it seems that the socket write error is meaningless.
>>>
>>> Is there a switch that needs flipping :)
>>>
>>> -- 
>>> Stephen P Rufle
>>> srufle at salmonllc dot com
>>> H:480-802-7173
>>> Yahoo IM: stephen_rufle
>>> AOL IM: stephen0rufle
>>>
>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>>
>>>
>>>
>>>
>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- Stephen P Rufle
>>> srufle at salmonllc dot com
>>> H:480-802-7173
>>> Yahoo IM: stephen_rufle
>>> AOL IM: stephen0rufle
>>> Microsoft Windows 2000 [Version 5.00.2195]
>>> (C) Copyright 1985-2000 Microsoft Corp.
>>>
>>> C:\Documents and Settings\srufle>maxq
>>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>>> INFO: MaxQ Proxy Recorder v0.97
>>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>>> INFO: Proxy server started on port: 8090
>>> C:\Documents and Settings\srufle>maxq -d
>>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>>> INFO: MaxQ Proxy Recorder v0.97
>>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>>> INFO: Proxy server started on port: 8090
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.ProxyServer run
>>> FINEST: New connection. Creating new RequestHandler thread.
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: read request header
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: wrote request header
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: no request body
>>> Oct 14, 2004 4:46:59 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>> FINE: recording url:
>>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq.Utils getParams
>>> FINE: parsing: folderID=695
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed request
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 1329 bytes
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 609 bytes
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 8192 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 2392 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 1003 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 952 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 960 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 990 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 785 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: transferred response
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseResponseCode
>>> FINE: HTTP response code: 200
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: content-type: text/html
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed response
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed server socket
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed client socket
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>>> FINEST: New connection. Creating new RequestHandler thread.
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: read request header
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: wrote request header
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: no request body
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>> FINE: recording url:
>>> http://maxq.tigris.o​rg/branding/images/i​con_arrowfolderopen2​_sml.gif
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed request
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>>> FINEST: New connection. Creating new RequestHandler thread.
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 238 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: transferred response
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseResponseCode
>>> FINE: HTTP response code: 304
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: No content-type header! First few lines:
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: http/1.1 304 not modified
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: connection: close
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: etag: "7486c7-298-c5488f40"
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>>> FINE: Ignoring response because content type is not known: null
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed response
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed server socket
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed client socket
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>>> FINEST: New connection. Creating new RequestHandler thread.
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: read request header
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: wrote request header
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: no request body
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>> FINE: recording url:
>>> http://maxq.tigris.o​rg/branding/images/
>>> icon_arrowfolderclosed1_sml.gif
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed request
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: read request header
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: wrote request header
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: no request body
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 238 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: transferred response
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseResponseCode
>>> FINE: HTTP response code: 304
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: No content-type header! First few lines:
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: http/1.1 304 not modified
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: connection: close
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: etag: "7486c3-1b9-c5488f40"
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>>> FINE: Ignoring response because content type is not known: null
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed response
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>> FINE: recording url:
>>> http://maxq.tigris.o​rg/branding/images/i​con_doc_sml.gif
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed request
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed server socket
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed client socket
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 238 bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: transferred response
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseResponseCode
>>> FINE: HTTP response code: 304
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: No content-type header! First few lines:
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: http/1.1 304 not modified
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: connection: close
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: etag: "7486cd-163-c5488f40"
>>> Oct 14, 2004 4:47:00 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>>> FINE: Ignoring response because content type is not known: null
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed response
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed server socket
>>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed client socket
>>> Oct 14, 2004 4:47:01 PM com.bitmechanic.maxq​.ProxyServer run
>>> FINEST: New connection. Creating new RequestHandler thread.
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: read request header
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: wrote request header
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: no request body
>>> Oct 14, 2004 4:47:02 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>> FINE: recording url:
>>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq.Utils getParams
>>> FINE: parsing: folderID=695
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed request
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.ProxyServer run
>>> FINEST: New connection. Creating new RequestHandler thread.
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: read request header
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: wrote request header
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: no request body
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 1329 bytes
>>> java.net.SocketException: Connection reset by peer: socket write
>>> error
>>> at java.net.SocketOutpu​tStream.socketWrite0​(Native Method)
>>> at java.net.SocketOutpu​tStream.socketWrite(​Unknown Source)
>>> at java.net.SocketOutpu​tStream.write(Unknow​n Source)
>>> at
>>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler
>>> .java:216)
>>> at
>>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler
>>> .java:204)
>>> at
>>> com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​176)
>>> at java.lang.Thread.run(Unknown Source)
>>> Oct 14, 2004 4:47:02 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>>> FINE: recording url: http://maxq.tigris.o​rg/docs/install.html​
>>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed request
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 1268 bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 1024 bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 8192 bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: read 2763 bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: wrote bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>>> moveAvailableBytes
>>> FINEST: buffered bytes
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: transferred response
>>> Oct 14, 2004 4:47:04 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseResponseCode
>>> FINE: HTTP response code: 200
>>> Oct 14, 2004 4:47:04 PM
>>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>>> parseContentType
>>> FINE: content-type: text/html
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: processed response
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed server socket
>>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>>> FINEST: closed client socket
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>>
> ---
> Frank Cohen, PushToTest, http://www.PushToTest.com, phone: 408 374 7426
> Author of "Java Testing and Design: From Unit Tests to Automated Web
> Tests"
> from Prentice Hall, details at http://thebook.pushtotest.com
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

Re: [maxq-users] Connection reset by peer

Author fcohen
Full name Frank Cohen
Date 2004-10-14 21:23:13 PDT
Message Hi Oliver: Expect a bunch of patches from me on the way MaxQ handles
errors. One change I already made to TestMaker when the proxy gets an
error from the host is to reply to the browser with an error page. You
can take them or leave them for MaxQ but they are definitely going into
TM. :-)

-Frank


On Oct 14, 2004, at 5:02 PM, Oliver Bock wrote:

> Stephen,
>
> I have changed MaxQ so that it is less noisy when it cannot write a
> response back to the browser. (It will still print a complaint to the
> DOS window, but it should not show a dialog nor print a stack trace.)
>
> Can you please get MaxQ using CVS and try that? This is the only
> change in CVS since v0.97.
>
>
> Oliver
>
> --
> On 15/10/2004, at 09:54, Stephen Rufle wrote:
>
>> Here is  stack trace , I turned on the -d parm for you :)
>>
>> This is what I think is happening  "but it also happens implicitly
>> if a user clicks on another link before the current page has finished
>> loading everything"
>>
>>
>> I get a "Broken pipe" message when the user cancels an operation on
>> the web browser.  This happens when the user clicks cancel, but it
>> also happens implicitly if a user clicks on another link before the
>> current page has finished loading everything.  I'm adding a fix to
>> suppress this error now.
>>
>> However your error may be different since you are getting
>> "Connection reset by peer", so perhaps yours is a different
>> situation.  You should see a Java stack trace in your DOS window when
>> this box appears.  Could you please reply with that?
>>
>>
>>    Oliver
>>
>> --
>> On 15/10/2004, at 04:10, Stephen Rufle wrote:
>>
>>
>> Is there a way for maxq to suppress the showing of the "MaxQ Error"
>> box when a  socket write error happens. It is confusing my tester ,
>> she is new to using the tool and is never sure that she actually
>> recorded the url that got the socket write error. I watched her and
>> it seems that the socket write error is meaningless.
>>
>> Is there a switch that needs flipping :)
>>
>> -- 
>> Stephen P Rufle
>> srufle at salmonllc dot com
>> H:480-802-7173
>> Yahoo IM: stephen_rufle
>> AOL IM: stephen0rufle
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>>
>>
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>>
>>
>>
>>
>>
>>
>> -- Stephen P Rufle
>> srufle at salmonllc dot com
>> H:480-802-7173
>> Yahoo IM: stephen_rufle
>> AOL IM: stephen0rufle
>> Microsoft Windows 2000 [Version 5.00.2195]
>> (C) Copyright 1985-2000 Microsoft Corp.
>>
>> C:\Documents and Settings\srufle>maxq
>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>> INFO: MaxQ Proxy Recorder v0.97
>> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
>> INFO: Proxy server started on port: 8090
>> C:\Documents and Settings\srufle>maxq -d
>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>> INFO: MaxQ Proxy Recorder v0.97
>> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
>> INFO: Proxy server started on port: 8090
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:46:59 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq.Utils getParams
>> FINE: parsing: folderID=695
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1329 bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 609 bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 8192 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 2392 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1003 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 952 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 960 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 990 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 785 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>> parseResponseCode
>> FINE: HTTP response code: 200
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: content-type: text/html
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/branding/images/i​con_arrowfolderopen2​_sml.gif
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 238 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>> parseResponseCode
>> FINE: HTTP response code: 304
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: No content-type header! First few lines:
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: http/1.1 304 not modified
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: connection: close
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: etag: "7486c7-298-c5488f40"
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>> FINE: Ignoring response because content type is not known: null
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/branding/images/
>> icon_arrowfolderclosed1_sml.gif
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 238 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>> parseResponseCode
>> FINE: HTTP response code: 304
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: No content-type header! First few lines:
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: http/1.1 304 not modified
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: connection: close
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: etag: "7486c3-1b9-c5488f40"
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>> FINE: Ignoring response because content type is not known: null
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/branding/images/i​con_doc_sml.gif
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 238 bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>> parseResponseCode
>> FINE: HTTP response code: 304
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: No content-type header! First few lines:
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: http/1.1 304 not modified
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: date: thu, 14 oct 2004 23:47:47 gmt
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b
>> dav/2 mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: connection: close
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: etag: "7486cd-163-c5488f40"
>> Oct 14, 2004 4:47:00 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
>> FINE: Ignoring response because content type is not known: null
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>> Oct 14, 2004 4:47:01 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:02 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url:
>> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq.Utils getParams
>> FINE: parsing: folderID=695
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.ProxyServer run
>> FINEST: New connection. Creating new RequestHandler thread.
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: read request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: wrote request header
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: no request body
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1329 bytes
>> java.net.SocketException: Connection reset by peer: socket write error
>> at java.net.SocketOutpu​tStream.socketWrite0​(Native Method)
>> at java.net.SocketOutpu​tStream.socketWrite(​Unknown Source)
>> at java.net.SocketOutpu​tStream.write(Unknow​n Source)
>> at
>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler.
>> java:216)
>> at
>> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler.
>> java:204)
>> at
>> com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​176)
>> at java.lang.Thread.run(Unknown Source)
>> Oct 14, 2004 4:47:02 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
>> FINE: recording url: http://maxq.tigris.o​rg/docs/install.html​
>> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed request
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1268 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 1024 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 8192 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: read 2763 bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: wrote bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
>> moveAvailableBytes
>> FINEST: buffered bytes
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: transferred response
>> Oct 14, 2004 4:47:04 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator
>> parseResponseCode
>> FINE: HTTP response code: 200
>> Oct 14, 2004 4:47:04 PM
>> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
>> FINE: content-type: text/html
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: processed response
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed server socket
>> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
>> FINEST: closed client socket
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
---
Frank Cohen, PushToTest, http://www.PushToTest.com, phone: 408 374 7426
Author of "Java Testing and Design: From Unit Tests to Automated Web
Tests"
from Prentice Hall, details at http://thebook.pushtotest.com


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

Re: [maxq-users] Connection reset by peer

Author oliverbock
Full name Oliver Bock
Date 2004-10-14 17:02:06 PDT
Message Stephen,

I have changed MaxQ so that it is less noisy when it cannot write a
response back to the browser. (It will still print a complaint to the
DOS window, but it should not show a dialog nor print a stack trace.)

Can you please get MaxQ using CVS and try that? This is the only
change in CVS since v0.97.


    Oliver

--
On 15/10/2004, at 09:54, Stephen Rufle wrote:

> Here is  stack trace , I turned on the -d parm for you :)
>
> This is what I think is happening  "but it also happens implicitly if
> a user clicks on another link before the current page has finished
> loading everything"
>
>
> I get a "Broken pipe" message when the user cancels an operation on
> the web browser.  This happens when the user clicks cancel, but it
> also happens implicitly if a user clicks on another link before the
> current page has finished loading everything.  I'm adding a fix to
> suppress this error now.
>
> However your error may be different since you are getting "Connection
> reset by peer", so perhaps yours is a different situation.  You should
> see a Java stack trace in your DOS window when this box appears. 
> Could you please reply with that?
>
>
>    Oliver
>
> --
> On 15/10/2004, at 04:10, Stephen Rufle wrote:
>
>
> Is there a way for maxq to suppress the showing of the "MaxQ Error"
> box when a  socket write error happens. It is confusing my tester ,
> she is new to using the tool and is never sure that she actually
> recorded the url that got the socket write error. I watched her and it
> seems that the socket write error is meaningless.
>
> Is there a switch that needs flipping :)
>
> -- 
> Stephen P Rufle
> srufle at salmonllc dot com
> H:480-802-7173
> Yahoo IM: stephen_rufle
> AOL IM: stephen0rufle
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
>
>
>
>
>
> --
> Stephen P Rufle
> srufle at salmonllc dot com
> H:480-802-7173
> Yahoo IM: stephen_rufle
> AOL IM: stephen0rufle
> Microsoft Windows 2000 [Version 5.00.2195]
> (C) Copyright 1985-2000 Microsoft Corp.
>
> C:\Documents and Settings\srufle>maxq
> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
> INFO: MaxQ Proxy Recorder v0.97
> Oct 14, 2004 4:46:39 PM com.bitmechanic.maxq.Main startGUI
> INFO: Proxy server started on port: 8090
> C:\Documents and Settings\srufle>maxq -d
> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
> INFO: MaxQ Proxy Recorder v0.97
> Oct 14, 2004 4:46:51 PM com.bitmechanic.maxq.Main startGUI
> INFO: Proxy server started on port: 8090
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.ProxyServer run
> FINEST: New connection. Creating new RequestHandler thread.
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: read request header
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: wrote request header
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: no request body
> Oct 14, 2004 4:46:59 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
> FINE: recording url:
> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq.Utils getParams
> FINE: parsing: folderID=695
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed request
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 1329 bytes
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 609 bytes
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:46:59 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 8192 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 2392 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 1003 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 952 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 960 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 990 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 785 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: transferred response
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
> FINE: HTTP response code: 200
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: content-type: text/html
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed response
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed server socket
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed client socket
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
> FINEST: New connection. Creating new RequestHandler thread.
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: read request header
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: wrote request header
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: no request body
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
> FINE: recording url:
> http://maxq.tigris.o​rg/branding/images/i​con_arrowfolderopen2​_sml.gif
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed request
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
> FINEST: New connection. Creating new RequestHandler thread.
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 238 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: transferred response
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
> FINE: HTTP response code: 304
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: No content-type header! First few lines:
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: http/1.1 304 not modified
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: date: thu, 14 oct 2004 23:47:47 gmt
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b dav/2
> mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: connection: close
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: etag: "7486c7-298-c5488f40"
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
> FINE: Ignoring response because content type is not known: null
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed response
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed server socket
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed client socket
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.ProxyServer run
> FINEST: New connection. Creating new RequestHandler thread.
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: read request header
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: wrote request header
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: no request body
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
> FINE: recording url:
> http://maxq.tigris.o​rg/branding/images/i​con_arrowfolderclose​d1_sml.gif
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed request
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: read request header
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: wrote request header
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: no request body
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 238 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: transferred response
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
> FINE: HTTP response code: 304
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: No content-type header! First few lines:
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: http/1.1 304 not modified
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: date: thu, 14 oct 2004 23:47:47 gmt
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b dav/2
> mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: connection: close
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: etag: "7486c3-1b9-c5488f40"
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
> FINE: Ignoring response because content type is not known: null
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed response
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
> FINE: recording url:
> http://maxq.tigris.o​rg/branding/images/i​con_doc_sml.gif
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed request
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed server socket
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed client socket
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 238 bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: transferred response
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
> FINE: HTTP response code: 304
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: No content-type header! First few lines:
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: http/1.1 304 not modified
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: date: thu, 14 oct 2004 23:47:47 gmt
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: server: apache/2.0.47 (unix) mod_ssl/2.0.47 openssl/0.9.6b dav/2
> mod_auth_mda/2.0 mod_jk/1.2.0 svn/0.23.0 mod_auth_svn/0.1
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: connection: close
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: etag: "7486cd-163-c5488f40"
> Oct 14, 2004 4:47:00 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processResponse
> FINE: Ignoring response because content type is not known: null
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed response
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed server socket
> Oct 14, 2004 4:47:00 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed client socket
> Oct 14, 2004 4:47:01 PM com.bitmechanic.maxq​.ProxyServer run
> FINEST: New connection. Creating new RequestHandler thread.
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: read request header
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: wrote request header
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: no request body
> Oct 14, 2004 4:47:02 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
> FINE: recording url:
> http://maxq.tigris.o​rg/servlets/ProjectD​ocumentList?folderID​=695
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq.Utils getParams
> FINE: parsing: folderID=695
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed request
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.ProxyServer run
> FINEST: New connection. Creating new RequestHandler thread.
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: read request header
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: wrote request header
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: no request body
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 1329 bytes
> java.net.SocketException: Connection reset by peer: socket write error
> at java.net.SocketOutpu​tStream.socketWrite0​(Native Method)
> at java.net.SocketOutpu​tStream.socketWrite(​Unknown Source)
> at java.net.SocketOutpu​tStream.write(Unknow​n Source)
> at
> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler.j
> ava:216)
> at
> com.bitmechanic.maxq​.RequestHandler.move​AvailableBytes(Reque​stHandler.j
> ava:204)
> at
> com.bitmechanic.maxq​.RequestHandler.run(​RequestHandler.java:​176)
> at java.lang.Thread.run(Unknown Source)
> Oct 14, 2004 4:47:02 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator processRequest
> FINE: recording url: http://maxq.tigris.o​rg/docs/install.html​
> Oct 14, 2004 4:47:02 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed request
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 1268 bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 1024 bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 8192 bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: read 2763 bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: wrote bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler
> moveAvailableBytes
> FINEST: buffered bytes
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: transferred response
> Oct 14, 2004 4:47:04 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseResponseCode
> FINE: HTTP response code: 200
> Oct 14, 2004 4:47:04 PM
> com.bitmechanic.maxq​.generator.AbstractC​odeGenerator parseContentType
> FINE: content-type: text/html
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: processed response
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed server socket
> Oct 14, 2004 4:47:04 PM com.bitmechanic.maxq​.RequestHandler run
> FINEST: closed client socket
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

Re: [maxq-users] Connection reset by peer

Author Stephen Rufle <srufle at salmonllc dot com>
Full name Stephen Rufle <srufle at salmonllc dot com>
Date 2004-10-14 16:54:19 PDT
Message Here is stack trace , I turned on the -d parm for you :)

This is what I think is happening *"but it also happens implicitly if a
user clicks on another link before the current page has finished loading
everything"
**
*

> I get a "Broken pipe" message when the user cancels an operation on
> the web browser. This happens when the user clicks cancel, *but it
> also happens implicitly if a user clicks on another link before the
> current page has finished loading everything*. I'm adding a fix to
> suppress this error now.
>
> However your error may be different since you are getting "Connection
> reset by peer", so perhaps yours is a different situation. You should
> see a Java stack trace in your DOS window when this box appears.
> Could you please reply with that?
>
>
> Oliver
>
> --
> On 15/10/2004, at 04:10, Stephen Rufle wrote:
>
>> Is there a way for maxq to suppress the showing of the "MaxQ Error"
>> box when a socket write error happens. It is confusing my tester ,
>> she is new to using the tool and is never sure that she actually
>> recorded the url that got the socket write error. I watched her and
>> it seems that the socket write error is meaningless.
>>
>> Is there a switch that needs flipping :)
>>
>> --
>> Stephen P Rufle
>> srufle at salmonllc dot com
>> H:480-802-7173
>> Yahoo IM: stephen_rufle
>> AOL IM: stephen0rufle
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
>> For additional commands, e-mail: users-help at maxq dot tigris dot org
>>
>>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>
>


--
Stephen P Rufle
srufle at salmonllc dot com
H:480-802-7173
Yahoo IM: stephen_rufle
AOL IM: stephen0rufle
Attachments

Re: [maxq-users] Connection reset by peer

Author oliverbock
Full name Oliver Bock
Date 2004-10-14 16:06:25 PDT
Message I get a "Broken pipe" message when the user cancels an operation on the
web browser. This happens when the user clicks cancel, but it also
happens implicitly if a user clicks on another link before the current
page has finished loading everything. I'm adding a fix to suppress
this error now.

However your error may be different since you are getting "Connection
reset by peer", so perhaps yours is a different situation. You should
see a Java stack trace in your DOS window when this box appears. Could
you please reply with that?


    Oliver

--
On 15/10/2004, at 04:10, Stephen Rufle wrote:

> Is there a way for maxq to suppress the showing of the "MaxQ Error"
> box when a socket write error happens. It is confusing my tester ,
> she is new to using the tool and is never sure that she actually
> recorded the url that got the socket write error. I watched her and it
> seems that the socket write error is meaningless.
>
> Is there a switch that needs flipping :)
>
> --
> Stephen P Rufle
> srufle at salmonllc dot com
> H:480-802-7173
> Yahoo IM: stephen_rufle
> AOL IM: stephen0rufle
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
> For additional commands, e-mail: users-help at maxq dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org

[maxq-users] Connection reset by peer

Author Stephen Rufle <srufle at salmonllc dot com>
Full name Stephen Rufle <srufle at salmonllc dot com>
Date 2004-10-14 11:10:29 PDT
Message Is there a way for maxq to suppress the showing of the "MaxQ Error" box
when a socket write error happens. It is confusing my tester , she is
new to using the tool and is never sure that she actually recorded the
url that got the socket write error. I watched her and it seems that the
socket write error is meaningless.

Is there a switch that needs flipping :)

--
Stephen P Rufle
srufle at salmonllc dot com
H:480-802-7173
Yahoo IM: stephen_rufle
AOL IM: stephen0rufle


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ma​xq.tigris.org
For additional commands, e-mail: users-help at maxq dot tigris dot org
Messages per page: