This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Java Interview Guide and have Anthony DePalma on-line!
See this thread for details.
The moose likes Other Java Products and Servers and the fly likes Thread behaviour of Resin Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Other Java Products and Servers
Bookmark "Thread behaviour of Resin" Watch "Thread behaviour of Resin" New topic

Thread behaviour of Resin

Raja Pratap

Joined: Feb 13, 2006
Posts: 2
I have the following configuration:


What happens if my server gets more than 250 requests concurrently? And how do we know that the server is loaded with requests. Please let me know.

Thanks in advance.
Raja Pratap

Joined: Feb 13, 2006
Posts: 2
I figured this out by myself.

When I have request number 251 and suppose if all the first 250 requests are still processing requests, then 251 request is queued until it has a free available thread to process the request.

This means that Resin queues all the requests if there are no available threads to process the request.
I agree. Here's the link:
subject: Thread behaviour of Resin
It's not a secret anymore!