Leon, Chuck:
Thankyou very much for (1) pointing out that tomcat has internal
session obj accesses, so go with something that accomplishes a
global fix and (2) just as important: what the current patches
are for 5.0.19+.
Leon, I went with your pre-compiled StandardSession.class and
replaced the
> Possibly the easiest thing to do is edit the StandardSession.java file
> and change the type of the attributes field to HashTable rather than
> HashMap, then rebuild the associated jar. The places that already
> synchronize on attributes can be left alone, since redundant synchs are
> allowed an
> From: Maurice Yarrow [mailto:[EMAIL PROTECTED]
> Subject: Synchronize wrapper for session obj attrib get/set
>
> For those not wishing to migrate at this time to 5.5.12
> (in our case, from 5.0.28 and jdk 1.4) would the following
> be sufficient for preventing deadlock acc
Hello Tomcat people
For those not wishing to migrate at this time to 5.5.12
(in our case, from 5.0.28 and jdk 1.4) would the following
be sufficient for preventing deadlock access of the session
objects ?
In a given servlet, say, ServletA, for example, might have:
HttpSession session = getS
