mesutyazici / tcpmon

Automatically exported from code.google.com/p/tcpmon
0 stars 0 forks source link

Large Post Completely Locks up TCPMON #14

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start up tcpmon via java web start, listening on port 8888, sending to port 
8080
2. Start up a server that can receive a post request on port 8080
3. Submit a post to the server via tcpmon where the post body contains a very 
large file (such as a 16MB war archive)

What is the expected output? What do you see instead?

Expected:
1. The connection shows up in the table at the top
2. The request should show up in the request area
3. The response should show up in the response area
4. The application should remain functional

Observed:
1. The connection is not displayed
2. After some time the request does show up
3. The response is never displayed
4. The UI stops responding and the program can only be killed via the operating 
system.

What version of the product are you using? On what operating system?
1.1

Please provide any additional information below.

In my case I was checking the action of apache httpclient when using FileEntity 
(which does not properly set up a multipart file upload as I had hoped still 
need to do the full MultipartEntity thing after all).

I suggest that you monitor the incoming data and beyond a certain size drop it 
to a temp file. If the user wants to see more than 100k (for example) of data, 
you can write it to a text file for them to view. Note that I am not suggesting 
that you make the binary data readable. That's not your problem, and probably 
not desireable since your tool is supposed to show exactly what transpired over 
the wire.

Original issue reported on code.google.com by gus.h...@gmail.com on 23 Nov 2011 at 6:47