From: Dennis Thrysøe [mailto:d...@geysirit.dk]
However, when such HTML files are added or modified to the webapp
(exploded directory) it takes something like 5 or 10 seconds before
they can be served by tomcat.
A wild stab in the dark based on something that happened to me...
How are you
On 7Jan, 2009, at 10:45, Peter Crowther wrote:
From: Dennis Thrysøe [mailto:d...@geysirit.dk]
However, when such HTML files are added or modified to the webapp
(exploded directory) it takes something like 5 or 10 seconds before
they can be served by tomcat.
A wild stab in the dark based on
On 7Jan, 2009, at 10:40, Dennis Thrysøe wrote:
Hi,
I have a tomcat 6 setup on linux (CentOS 5) and see some odd
behaviour.
There are some JSP's that include (in a custom tag with
pageContext.include()) static HTML resources that are in the webapp.
However, when such HTML files are added
Dennis Thrysøe wrote:
On 7Jan, 2009, at 10:40, Dennis Thrysøe wrote:
Hi,
I have a tomcat 6 setup on linux (CentOS 5) and see some odd behaviour.
There are some JSP's that include (in a custom tag with
pageContext.include()) static HTML resources that are in the webapp.
However, when such
From: Dennis Thrysøe [mailto:d...@geysirit.dk]
Subject: Re: Delay / caching of resources?
I have now found a potential explanation with the help of a good
debugger: StandardContext.setCacheTTL()
Who's calling that API? The only internal calls I find in Tomcat simply
propagate the value
On 7Jan, 2009, at 15:44, Caldarale, Charles R wrote:
From: Dennis Thrysøe [mailto:d...@geysirit.dk]
Subject: Re: Delay / caching of resources?
I have now found a potential explanation with the help of a good
debugger: StandardContext.setCacheTTL()
Who's calling that API? The only internal
