> From: David kerber [mailto:[EMAIL PROTECTED]
> Subject: Re: java.util.timer firing twice
>
> Now to come up with a workaround; I should be able to just
> check to see which context the timer is running under in
> the, and bail out if it's not the one I want, shouldn&
That's got to be it; I have the app deployed (intentionally) both at its
own context root, and as the ROOT context. It never crossed my mind
that that would screw up my timers, though it certainly should have.
Now to come up with a workaround; I should be able to just check to see
which conte
> From: David kerber [mailto:[EMAIL PROTECTED]
> Subject: java.util.timer firing twice
>
> I have a situation where a java.util.timer object scheduled
> to run once per day (by using .scheduleAtFixedRate) is firing
> two times at once
Any chance your webapp has actually been deployed twice, cau
