You could have the servlet write a file that is then checked for by an
external application. If the file exists then the external app could kill
the tomcat.
Rob
-Original Message-
From: afolli [mailto:[EMAIL PROTECTED]
Sent: 25 July 2008 09:20
To: users@tomcat.apache.org
Subject: Stop
You could use a script to edit your appconfig.xml with the value. Try the
"replace" command that comes with MySQL:
APP_PATH=/my/app/lives/here
replace "to-be-replaced" $APP_PATH -- appconfig.xml
Then do your tomcat startup as you have suggested by setting a system
property on the command line wit
The XYZ is just a placeholder. None of the actual classes are Tomcat
classes, they are all servlets we have written.
Rob
-Original Message-
From: Len Popp [mailto:[EMAIL PROTECTED]
Sent: 23 July 2008 14:37
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Tomcat cannot find infrequen
I do not know about c3p0, I just know that with the connection pools we use,
you must return a connection to the pool once you are finished with it
because our pools have a limit on the number of connections that can be
created in the pool. This stops the database getting too many requests.
Rob
Are the connections being returned to the pool after use? If they are not
then your application could quickly run out of connections.
Rob
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Silvio
Rainoldi
Sent: 23 July 2008 11:07
To: users@tomcat.apache.org
I have a very large web application, running on three tomcats, which has
been running for many years.
There was a change made to the web application overnight, to add the
following jar files to the webapp/WEB-INF/lib directory:
avalon-framework-cvs-20020806.jar
batik.jar
crimson_1_1_3.jar
icu4j_2
