service to crash, (not the
JVM), when using a connection pool and the database server is busy.
Is this a windows or a Tomcat issue? It is a practical issue for Tomcat
users - the service is much more convenient.
Iain.
"Iain Sanderson" <[EMAIL PROTECTED]>
04/03/2003 03:51 PM
P
that needs
to be backed up and you run 24x7, you will need to make other arrangements
to back that data up.
Chuck
-Original Message-
From: Iain Sanderson [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 9:32 AM
To: [EMAIL PROTECTED]
Subject: Tomcat unstable - Dr. Watson. Why?
He
Can't help you much more, as it seems a Windows issue. I've managed to
avoid running servers on windows machines so far and I don't plan to
start soon ;)
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: Iain Sanderson [mailto:[EMAIL PROTECTED]
>Sen
not there, that's a good thing, it means your JVM
did not crash.
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: Iain Sanderson [mailto:[EMAIL PROTECTED]
>Sent: Thursday, April 03, 2003 2:16 PM
>To: Tomcat Users List
>Subject: RE: Tomcat unstable - Dr.
Hi,
regarding
>hs_err_..etc
I couldn't find a file named anything like this on my server. I do have
stout.log and sterr.log , set in the registry for the JVM for Tomcat
service startup. Is this what you mean?
Iain
"Shapira, Yoav" <[EMAIL PROTECTED]>
04/03/2003 01:16 PM
Please respond
Thanks,
>Is DBCP or something else doing keep-alive / sanity checks on the DB
connections? Or other keep-alive / ping type activity to the DB server?
If so, these checks could be hanging, or just spinning in a deadlock, if
the DB server is too busy to respond.
There are no other keep-alive check
Hello,
Tomcat is crashing on my application server when my database server is
busy with a running backup, which is every night from 12am to 7am ( 80
Gb).
I'm running Tomcat 4.22 on Windows NT sp6 using the Java 1.41 VM as a
service with the -Xxms256m -Xxmx256m switches set in the registry
Neal,
I use Poolman and have found it excellent. A testimony to it's usefulness
is that folk are still recommending it 9 months after its developer stopped
supporting it and issued the final 2.1b release.
You'll find that Poolman's connection code is near identical to that which
you've shown, so
Hi,
Has anyone else seen a memory leak using Tomcat 4.1/JDK 1.4.1 and a Struts
web application? I was using the Coyote Http 1.1 connectors on port 8080
and 443 ( for SSL) in Server XML, and found my web app died after 24 hours
or so with an OutOfMemoryException. I suspected a memory leak and t
