Hi,
I have enable 'debug' mode and find such lines in mode_jk log.
There are other types of lines also
Mon Oct 07 10:39:34 2013][993:1188796736] [debug] service::jk_lb_worker.c
(1157): service worker=node2 route=node2\par
Can I know how I should parse this log to prove that
On Oct 7, 2013, at 1:00 AM, Anu Prab anupr...@gmail.com wrote:
Hi,
The Tomcat version I am using is 7.0.40 and the connection pool is
tomcat-jdbc. I am having trouble configuring the connection pool. The
configuration does not trouble as long as I do not include initialSize and
factory
On Oct 7, 2013, at 2:57 AM, mohan.radhakrish...@polarisft.com wrote:
Hi,
I have enable 'debug' mode and find such lines in mode_jk log.
There are other types of lines also
Mon Oct 07 10:39:34 2013][993:1188796736] [debug] service::jk_lb_worker.c
(1157): service worker=node2
Hi,
The Tomcat version I am using is 7.0.40 and the connection pool is
tomcat-jdbc. I am having trouble configuring the connection pool. The
configuration does not trouble as long as I do not include initialSize
and factory attributes. But when I include any of these two, Tomcat
On Oct 7, 2013, at 6:52 AM, Anu Prab anupr...@gmail.com wrote:
Hi,
The Tomcat version I am using is 7.0.40 and the connection pool is
tomcat-jdbc. I am having trouble configuring the connection pool. The
configuration does not trouble as long as I do not include initialSize
Ok. I am already doing that. I thought mod_jk logs can be parsed using
something like awstats.
Mohan
From: Daniel Mikusa dmik...@gopivotal.com
To: Tomcat Users List users@tomcat.apache.org
Date: 10/07/2013 04:21 PM
Subject:Re: parse mod_jk log
On Oct 7, 2013, at 2:57 AM,
On 10/07/2013 01:50 PM, mohan.radhakrish...@polarisft.com wrote:
Ok. I am already doing that. I thought mod_jk logs can be parsed using
something like awstats.
Take a look at
http://tomcat.apache.org/connectors-doc/reference/apache.html
JkRequestLogFormat will format the line as you like
You
On Oct 7, 2013, at 7:50 AM, mohan.radhakrish...@polarisft.com wrote:
Ok. I am already doing that. I thought mod_jk logs can be parsed using
something like awstats.
Probably. My point was why bother, if you already have that information in the
access logs. Especially if you have to increase
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Anu,
On 10/7/13 6:52 AM, Anu Prab wrote:
Yes Dan, you are right. I placed the jar in the correction location
now.. Thanks for the help. However, am now facing the below
exception.
WARNING: Unexpected exception resolving reference
Don't top post.
From: Daniel Mikusa dmik...@gopivotal.com
To: Tomcat Users List users@tomcat.apache.org
Date: 10/07/2013 04:21 PM
Subject:Re: parse mod_jk log
On Oct 7, 2013, at 2:57 AM, mohan.radhakrish...@polarisft.com wrote:
Hi,
I have enable 'debug' mode and
Hi,
Tomcat : 7.0.33
Java : 6
JDBC Pool : 1.0.9.3
Grails : 1.3.9
We are running a grails app that is using the tomcat JDBC thread pool, what
we are seeing is the idle connections falling below minIdle and then
continuously heading towards zero over the course of a few hours.
I think I understand
11 matches
Mail list logo