ou please let me know whether you consider this as a bug?
Thx,
Ohad
On Mon, Sep 27, 2010 at 12:04 PM, sebb wrote:
> On 26 September 2010 15:00, Ohad Shacham wrote:
> > Hi,
> >
> >
> > In addition to the behavior we experienced in function setAttribute. We
>
Given that there is a violation, and the proposed solution is simpler, would
you take it in the next release?
Thanks,
Ohad
On Sun, Sep 26, 2010 at 10:42 PM, Tim Whittington wrote:
> This is technically a race condition, but given the vague information
> provided in ServletContextAttributeEvent
Hi,
In addition to the behavior we experienced in function setAttribute. We also
experienced another atomicity violation in function removeAttribute.
The following code is located at the beginning of function removeAttribute
at class ApplicationContext. This code fragment intends to check whethe
Hi,
We are building a tool for detecting non atomic usages of concurrent
collections.
We analyzed Tomcat’s code using our tool and found the following behavior:
The following code is located at the beginning of function setAttribute at
class ApplicationContext. This code fragment intends t
Hi,
We are writing a tool to detect atomicity violations in usage of
ConcurrentHashMap.
We have run the tool that reported an atomicity violation in functions get
and put of class ConcurrentCache.
The following code shows the put function of the ConcurrentCache:
public void put(K k, V v
Hi,
We are writing a tool to detect atomicity violations in usage of
ConcurrentHashMap.
We have run the tool that reported an atomicity violation in functions get
and put of class ConcurrentCache.
The following code shows the put function of the ConcurrentCache:
public void put(K k, V v
Hi,
I would like to run tomcat for testing, I am looking for test cases with
aggressive workload.
Could you please let me know whether there exists a testing/benchmarking
suite for tomcat that I can use?
Thanks,
Best Regards,
Ohad
Hi,
I noticed that in version 6.0.20 several Hashtables and HashMaps were
replaced by ConcurrentHashMaps. I have noticed that many Hashtables were not
replaced; therefore, I assume that a contention detection tool was used to
identify the contended Hashtables. I would be happy to know if this is
