----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Conrad Chan wrote:
>
>
> Well it is a long story about why I need to do this. I realize that a JServ
> session is inexpension but not the rest of the resources we need to use for
> each session. When we have a new session, we need to have a connection to
> our middle-tier server, the third party product we have been using will then
> allocate 2 more threads for the new connection. (Yes I can't believe that
> either) In a high load period (say 1000 users), our linux server will run
> out-of threads rapidly (Linux by-default can only have around 500
> threads/processes) and JServ will then die.
>
> In our case, it will make more sense to limit the number of sessions instead
> of number of connections.
>
> Any suggestion will be appreciated.
>
load-balancing could maybe help ? At least it's really low cost on Linux
x86 boxes.
Another solution is to use a good thread implementation Operating System
like Solaris or Solaris (or Solaris ...)
I guess that if you have to connect to another tier, you use some
transactionnal services ? So you'll have to rollback something, which is
probably more CPU expensive than a blocked thread ... (even
encapsulated)
Jean-Luc
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
