This week's book giveaway is in the Java in General forum.
We're giving away four copies of Think Java: How to Think Like a Computer Scientist and have Allen B. Downey & Chris Mayfield on-line!
See this thread for details.
Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

How to deal with slow client connections?

 
John De Vries
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I'm using Tomcat to serve static files. But I often get clients that are to slow, and thus causing the max thread limit to be reached. For example this client:

Connection:
-Stage: Service (other stages examples are: Finishing, Ready, Keepalive).
-Time: 1414057 ms (23 minutes)
-B Sent: 24 KB
-B Recv: 0 KB
-Client: 217.8.xxx.xxx
-VHost: wwww.xxxxxxx.com
-Request: GET /xxxx/xxxxx.jpg HTTP/1.1


Other Tomcat info:
JVM:
-Free memory: 47.58 MB Total memory: 508.06 MB Max memory: 508.06 MB
http-8080:
-Max threads: 150 Current thread count: 87 Current thread busy: 29
-Max processing time: 1390120 ms Processing time: 70988.9 s Request count: 118298 Error count: 2686 -Bytes received: 0.00 MB Bytes sent: 1657.52 MB

My Tomcat settings are defaults plus:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="3000"
maxThreads="150"
enableLookups="false"
redirectPort="8443" />




This slow client (above) is retrieving .jpg file, and used 23 minutes to transfer only 24KB. I would like Tomcat to automatically kill of timeout these connections. How can I achieve this?
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18152
52
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
24KB in 23 minutes isn't just a slow data link. I used to consider 24KB about optimal page size back when I dialed in at 9600 baud, and you can bet I wasn't waiting 23 minutes for each page.

Either there's a serious network configuration issue, the application extraordinarily inefficient, or there's a whole raft of side information that's bloating up that presumed 24KB into a multi-megabyte actual transfer.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic