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 checks on the server.
>-Xms etc...
Yous are right about the switches, my typo. Memory doesn't seem to be an
issue. With verbose GC, memory is never near its limits during a failure
and GC seems to work as it should. Full GC brings the heap down to about
50MB and it stays there for days without obvious leakage.
> hs_err_[pid]
I'll check this - didn't know about it. Thanks very much!
>Is it acceptable .....
Yes, these response times are accepable in the middle of the night, but
how can I dynamically reconfigure the pool/ tomcat settings as you
suggest?
Iain.
"Shapira, Yoav" <[EMAIL PROTECTED]>
04/03/2003 01:16 PM
Please respond to "Tomcat Users List"
To: "Tomcat Users List" <[EMAIL PROTECTED]>
cc:
Subject: RE: Tomcat unstable - Dr. Watson. Why?
Howdy,
Does your app server need to be available when your DB server is doing
backups? If not, you could always restart the app server at 7am.
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.
>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 for
You mean -Xmx256m and -Xms256m, right? What if you allow more memory?
>There is no information in Tomcat's logs at all. Windows just shuts
down
Is there a JVM internal crash log? This is typically a hs_err_[pid]
file in the current working directory of the JVM.
>the server are large ( Operating room schedules etc. Queries take 0.15
to
>0.2 seconds, but page refreshes in Tomcat 5-6 seconds, which is
>acceptable. With incremental GC this increases to 17 seconds, which is
>not.)
Is it acceptable for the midnight-7am period? Or not acceptable even
during this time?
>I'm sure the problem is due to database connections, but I can't fault
my
>code. I'm using Tomcat's JNDI datasource pool (commons DBCP), set in
>server.xml. I have been very careful to close all my connections using
>the following code straight out of Tomcat's documentation (see below)
Maybe you should add something to your app server that closes all DB
connections at midnight, and until 7am establishes DB connections on
demand, i.e. doesn't go through a pool. This will help isolate the
problem.
Yoav Shapira
Millennium ChemInformatics
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged. This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your
computer system and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
