Solution:
It's easy to specify a context.xml. I'm already using a special one for
injection of performance-gauging configs, and a valve is attachable to a
host, engine, or context. I attached access log valves to each context
with the requisite conversion patterns in each app's context.xml.
On
Hi all,
I've got a unique deployment -- I'm using the new tag in the
plugin to deploy multiple webapps in an embedded plugin, then running
load/integration tests against them. I have all that working great.
Problem is I need to analyze the access logs and the default format with
the plugin does
On 19/12/2012 19:41, Josh Gooding wrote:
> Hey group,
>
> Just a quick question. Can I utilize the parallel deployment in conjunction
> with the war farmer for the cluster? It should be independent right?
Yes and yes.
Mark
-
On Dec 19, 2012, at 8:57 AM, vicky007aggar...@yahoo.co.in wrote:
> My tomcat 6.x is using currently is using the default logging i.e JULI.
Please include the specific version of Tomcat that you are using. There are 36
releases in the 6.0.x branch, it helps to know exactly which one you are usin
My tomcat 6.x is using currently is using the default logging i.e JULI.
But my application deployed on it is using log4j which was working fine on
jboss earlier but when i deployed the same on tomcat i got below error
+
SEVERE:Error listener start
When i googled i
Hi,
server.xml
worker.properties
worker.*tomsrv02*.type=ajp13
worker.*tomsrv02*.host=172.17.1.45
worker.*tomsrv02*.port=8009
worker.*tomsrv02*.lbfactor=1
worker.*tomsrv02*.connection_pool_timeout=20
worker.tomsrv02sec.type=ajp13
worker.tomsrv02sec.host=172.17.1.45
worker.tomsrv02sec.port=
