----------------------------------------------------------------
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!!!
----------------------------------------------------------------
on 12/17/99 6:31 PM, Bernie Bernstein <[EMAIL PROTECTED]> wrote:
> I'd recommend upgrading to the latest version in CVS rather than the
> Jserv1.1b3 package. When I was running the stock 1.1b3 I noticed a similar
> problem. I think Jean-Luc or Jon fixed a thread leak (or was it a socket
> leak?). Now it seems better. We aren't running 1.1 in production yet, but
> we've been doing fairly well with 1.0 for now until we take the plunge to 1.1.
>
>
> Bernie
I concur with Bernie. Use the stuff in CVS. It is definitely a lot more
stable than 1.1b3.
You can get a snapshot from here:
<http://www.working-dogs.com/daily/>
I will be checking my email and be ready to help if I can. Also, make sure
that you are closing all of your database connections. You might also want
to use the various system resources tools (like top) to see where the system
is spending all of its time. Adding some logging to your servlet may also
help.
Also, make sure that you are using the *production* release JVM for Solaris
and not the *reference* release. That will make a huge difference in speed.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
--
--------------------------------------------------------------
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]
