I'm using Tomcat with juli. I'm using java.util.logging.ConsoleHandler to
handle logging output.
My logging.properties looks like the following:
handlers = java.util.logging.ConsoleHandler
.handlers = java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level = FINE
Connector port=8080 protocol=HTTP/1.1 maxKeepAliveRequests=1
connectionTimeout=2
redirectPort=8443 /
On 02/03/2010 02:14 PM, youngm wrote:
(This is a new thread spawned from my Tomcat 6.0.24 Google Chrome
thread
with better information)
I'm running
I am having a similar problem though I only see this problem in Google
Chrome. I request my home page in chrome and it takes 100 sec to load the
page. If I load the page in Firefox it loads excellent. I downgrade to
tomcat 6.0.20 and everything works great in chrome.
This is hitting a server
(This is a new thread to discuss a problem I accidentally posted to the
Tomcat access is very slow)
I'm having a performance problem on Tomcat 6.0.24 and Google Chrome. I
request my home page in chrome and it takes 100 sec to load the page. If I
load the page in Firefox it loads excellent. I
what bytes the browser sent when in the request, for
example, and whether the browser half-closed the socket.
Also, which Connector are you using? What happens if you use a different
one?
Cheers,
- Peter
On 3 February 2010 17:37, youngm you...@gmail.com wrote:
I am having
information.
Otherwise consider this thread closed unless anyone else has happened to see
a similar problem.
Mike
youngm wrote:
(This is a new thread to discuss a problem I accidentally posted to the
Tomcat access is very slow)
I'm having a performance problem on Tomcat 6.0.24 and Google Chrome
(This is a new thread spawned from my Tomcat 6.0.24 Google Chrome thread
with better information)
I'm running Tomcat 6.0.24, Sun JDKx86 6u18, Windows 7 64, Firefox and Chrome
browser.
I've noticed that for about the first 1-3 min after my tomcat instance has
started some of my requests that
Thanks for your help guys. I've never really considered modifying a .war
outside of the normal build process an acceptable thing to do. But, it
appears that is the recommended approach from the Tomcat community so I'll
work with my middleware organization to see if we can get something like
Ok, so to sum up this is what I've gathered.
Here is my hypothetical situation. I have a .war running in production.
This war embeds an oracle driver in its WEB-INF/lib. Middleware discovers
that there is a security vulnerability in this oracle driver and need to do
an emergency upgrade of
Very bad idea. Search the archives for a long list of things that go
wrong when you start changing the class path. Not to mention that would
make the new driver visible to all web applications not just the web app
that needed the new jar file. And you'd need to restart Tomcat for the
changes to
I am designing my production Tomcat 6 system and would like to have a
classloader where I can put emergency patch jars (e.g. database drivers,
etc) and configuration (e.g. tweaked spring config).
These artifacts would need to be loaded in a classloader between the System
Classloader and the
Put expanded classes into WEB-INF/classes.
Likewise, in CATALINA_BASE/lib
So CATALINA_BASE/lib jars and classes are used before the application
(WEB-INF/lib and /classes)?
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html under Class
Loader Definitions seems to indicate
12 matches
Mail list logo
