tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Mikusa <dmik...@gopivotal.com>
Subject Re: parse mod_jk log
Date Mon, 07 Oct 2013 13:39:36 GMT
On Oct 7, 2013, at 7:50 AM, mohan.radhakrishnan@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 the log level to debug which would increase the size of
your logs.

Having said that, I have no idea what your requirements are for this project.  I was just
throwing out there in case you hadn't considered the access logs.  If it's something you've
looked at or if it won't work for your requirements, feel free to ignore my outburst.

Dan


> 
> 
> Mohan
> 
> 
> 
> From:   Daniel Mikusa <dmikusa@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.radhakrishnan@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 route=node2\par
>> 
>> Can I know how I should parse this log to prove that connections are 
>> actually routed to two nodes( two tomcat instances) properly ?
> 
> Could you just look at the access logs on the two Tomcat nodes?  Those 
> would certainly show when a request is routed to each node (i.e. node-aa 
> will have only records for requests sent to node-a and vise versa).  That 
> would also be better than running with debug log level enabled all the 
> time.
> 
> Dan
> 
>> What line 
>> should I be looking for ?
>> 
>> I plan to use 'R' to graph.
>> 
>> Thanks,
>> Mohan
>> 
>> 
>> This e-Mail may contain proprietary and confidential information and is 
> sent for the intended recipient(s) only.  If by an addressing or 
> transmission error this mail has been misdirected to you, you are 
> requested to delete this mail immediately. You are also hereby notified 
> that any use, any form of reproduction, dissemination, copying, 
> disclosure, modification, distribution and/or publication of this e-mail 
> message, contents or its attachment other than by its intended recipient/s 
> is strictly prohibited.
>> 
>> Visit us at http://www.polarisFT.com
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> 
> 
> 
> This e-Mail may contain proprietary and confidential information and is sent for the
intended recipient(s) only.  If by an addressing or transmission error this mail has been
misdirected to you, you are requested to delete this mail immediately. You are also hereby
notified that any use, any form of reproduction, dissemination, copying, disclosure, modification,
distribution and/or publication of this e-mail message, contents or its attachment other than
by its intended recipient/s is strictly prohibited.
> 
> Visit us at http://www.polarisFT.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message