----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Dan, we have to stick with the IBM JDK with two big reason. First and the
most important reason, IBM JDK is A LOT faster and secondly we are going to
have SMP box that needs native-threads to take advantage from it.
Conrad
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dan
> Milstein
> Sent: Tuesday, November 09, 1999 1:03 PM
> To: Java Apache Users
> Subject: Re: Out of threads in linux
>
>
> ----------------------------------------------------------------
> 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!!!
> ----------------------------------------------------------------
>
> You might consider using a different JDK which does not use
> native threading.
> The Blackdown JDK, for example, will let you use green
> threads (user-level
> threads). The native threading / user threading tradeoffs
> are not simple, so
> you may actually see improved performance with user threads.
>
> -Dan
>
> Conrad Chan wrote:
> >
> > ----------------------------------------------------------------
> > 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!!!
> > ----------------------------------------------------------------
> >
> > We are using Apache 1.3.6 + JServ 1.0 + IBM JDK 118 on
> Mandrake 6.1 on a
> > production environment. We encounter Jserv keeps dying
> frequently ( 5-7
> > times a day) with the error messages 'OutOfMemoryError:
> cannot create more
> > thread'. We understand that there is a maximum limit on
> the number of
> > processes under Linux environment. But even if we specify under
> > jserv.properties with security.maxConnections=100, we still
> encounter the
> > same problem. Our first question is how come JServ still
> allocates so much
> > threads (I could create more than 200 threads manually to
> duplicate the
> > problem) even if we ask it to only allow 100? Is there any
> workaround or
> > other setting we can have to avoid JServ to crash?
> >
> > Anyone did try to run JServ1.1 on production environment?
> We are considering
> > upgrade to the new version and use its load balancing
> feature but wondering
> > how well it can perform since it is still in beta. Any comment or
> > recommendation is appreciated.
> >
> > Conrad
> >
> > --
> > --------------------------------------------------------------
> > 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]
>
> --
>
> Dan Milstein // [EMAIL PROTECTED]
> Member of Technical Staff // Capital Knowledge Partners
>
>
> --
> --------------------------------------------------------------
> 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]
>
--
--------------------------------------------------------------
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]
