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 context the timer is running under in the, and bail out if it's
not the one I want, shouldn't I?
Thanks!!!!!!!!!!!
D
Caldarale, Charles R wrote:
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, causing two
copies of every singleton object to be created? Double deployment can
be provoked unintentionally with erroneous <Context> elements.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
