This should be fixed now. If you could test the latest nightly, it would be
a big help.
- Original Message -
From: Hugh J. L. [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Monday, August 19, 2002 1:42 AM
Subject: Duplicate Contexts in reloading. Probably a sync bug in Tomcat 3.3.
Hi,
If two requests enter ReloadInterceptor.contextMap()
simultaneously and both reload context, it causes
duplicate context reloading.
-- messages --
2002-08-19 16:15:16 - ContextManager: Removing context
DEFAULT:/examples
2002-08-19 16:15:16 - ContextManager: Removing context
DEFAULT:/examples
2002-08-19 16:15:16 - ContextManager: Adding context
DEFAULT:/examples
2002-08-19 16:15:16 - ContextManager: Adding context
DEFAULT:/examples
-- messages --
As a result, ContextManager.contextsV has duplicate
Context object, while ContextManager.contexts doesn't
have since it is Hashtable -- the first is replaced.
I found this problem and then simulated it in JBuilder
with its debugging functions.
I think that it is not enough to sync DependManager
only. It is necessary to sync some code in
ReloadInterceptor.contextMap().
So far don't know if this problem will cause further
errors.
Thanks.
__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
