Len, you are a genius (in my kitchen anyway). That's exactly the issue. I
just checked. I had it set to reload during development, but we don't need
it anymore.
Thanks again.
Z.
Len Popp wrote:
>
> The key is this line:
> INFO: Reloading this Context has started
> It looks like the webapp i
The key is this line:
INFO: Reloading this Context has started
It looks like the webapp is started, and then *immediately* it's
re-loaded & started again. Reloading happens automatically if the
app's has the attribute reloadable=true and the app is
modified. It could be that the timestamp on one o
>
> shy away from these 2.3 Servlet listeners which do not understand
> load-on-startup parameter
> a.. BEA WebLogic up to 8.1 SP2
> b.. IBM WebSphere 5.x
> c.. Oracle OC4J 9.0.3
> Anyone else?
> Martin-
> - Original Message -
> From: "Sparecreative&quo
-on-startup parameter
a.. BEA WebLogic up to 8.1 SP2
b.. IBM WebSphere 5.x
c.. Oracle OC4J 9.0.3
Anyone else?
Martin-
- Original Message -
From: "Sparecreative" <[EMAIL PROTECTED]>
To:
Sent: Saturday, March 29, 2008 9:30 PM
Subject: Re: ServletContextListener Query
The original formatting was all screwed up. My apologies.
I'm seeing an issue when using a ServletContextListener on Tomcat 6.0.13.
Tomcat is triggering the contextInitialized method at startup but then
shortly after fires off the contextDestroyed method, followed by the
contextInitialized again.
