FYI
> [EMAIL PROTECTED] wrote:
>> Well, i rechecked all twice, i't a new fresh install.
>> The only old thing is the app context, that is not embedded into server.xml
>> but as a standalone file.
>> I still had a doubt about the jk module that was compiled for 4.1.10, but i
>> downloaded 4.1
Some of actually use both logs(apache and tomcat) for varios reasons.
The tomcat logs allow us to look at how well load balancing is working
across all our tomcat instances.
If bug patch 12145 were examined - tomcat logging would be much richer
allowing Request & Session Attributes, Cookies, a
[EMAIL PROTECTED] wrote:
> Well, i rechecked all twice, i't a new fresh install.
> The only old thing is the app context, that is not embedded into server.xml
> but as a standalone file.
> I still had a doubt about the jk module that was compiled for 4.1.10, but i
> downloaded 4.1.12 connectors an
Hi, i'm migrating my webapp from 4.1.10 to 4.1.12, but i guess the access
log has gone a bit screwed up.
In the context descriptor of the app i have a valve like this:
that worked like a charm with 4.1.10.
Now with 4.1.12 have a look to a sample of what i see into it.
(Sorry for the weird look
