--
Bibhas Bhattacharya wrote:
>
> --
>
> Gunther,
>
> Pierpaolo Fumagalli has understood and answered the question right.
>
> Thread pooling is a common mechanism that takes the advantage of threads
> (as you have correctly pointed out) to the next level. Instead of creating
> a fresh new thread for every request, the server keeps a pool of thread.
> When a request comes in, it routes the request to one of the threads.
> Several algorithms are available to pick the thread (round robin, random,
> or history based) for best load balancing.
Does anyone know what impact this will have on ThreadLocal Variables and
Transactions
asociated with threads?
I think the reuse of threads might break some code, which relies on
having a new thread
each time a new request comes in.
Stefan
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
