I am moving to jk (1.2.18) from jk2 & am having problems with the
workers.properties file. I have separate apache and tomcat servers. Here is
my working jk2 (workers2.properties) config:
[logger]
level=ERROR
[config:]
file=${serverRoot}/conf/workers2.properties
debug=0
debugEnv=0
[uriMap:]
info=M
Opps, sorry I forgot to mention that I am running continuous pings between
the tomcat and database server and not seeing any drops.
james
No, different machines. But, it works all day and works right after a
restart of tomcat.
j
On 4/28/06, ALEX HYDE <[EMAIL PROTECTED]> wrote:
Are they on the same machine? If not it could be a
firewall issue? It could be alot of things but that's
a start.
--- james edwards <[E
I am running 3 servers; Apache, Tomcat (5.5.16, java version "1.5.0_06",
Informix JDBC-1.3.00.JC3) and Informix (7.31.UD2).
After the app has been idle for several hours tomcat cannot access the
database. Netstat shows not connections to the database
and tcpdump shows no traffic at all going the d
On 4/25/06, David Kerber <[EMAIL PROTECTED]> wrote:
It kind of sounds like your connection to the database is timing out.
Does this happen after the tomcat instance in question has been idle for
an extended time?
Yes, overnight. Perhaps when the dB is brought down to do a backup.
We will test ton
I read the relase notes for tomcat and tried setting "ulimit -s 2048" in
the start script (I restarted the app). I just noticed that when tomcat
"hangs" and I can still pull up the default tomcat page if I go the the
tomcat server and load the url http://servername:8088.
I am wondering if my prob
We are running separate tomcat and apache servers, the http requests are
being proxied from the apache server to the tomcat server.
Tomcat connects to an informix database; our application is a webpage that
allows users to make queries against the dB and report the results
in html.
Here is the box
