RE: StaticBucketMap, Re: DO NOT REPLY [Bug 30148] - Internal serverError

[Corin Moss]

Hi There,

Does the current CVS head for ECM reflect the removal of the
StaticBucketMap?  If so, is the repository the same it always was (on
cvs.apache.org)?  I'm still getting references to the class in
AbstractThreadManager and TPSPThreadManager after an update.

Thanks,

Corin

> -Original Message-
> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 10, 2004 5:49 PM
> To: [EMAIL PROTECTED]
> Subject: StaticBucketMap, Re: DO NOT REPLY [Bug 30148] -
> Internal serverError
>
> [EMAIL PROTECTED] wrote:
> > .
> >
> > --- Additional Comments From [EMAIL PROTECTED]
> > 2004-08-10 11:01 --- The bug was fixed in 2.1.4. Carsten kindly
> > replaced any reference to the StaticBucketMap with a synchronized
> > HashMap (not nice, but it works). This was done in the Excalibur
> > ComponentManager package. Commons-Collections still has the
> non-threadsafe StaticBucketMap in it.
>



CAUTION: This e-mail and any attachment(s) contains information
that is intended to be read only by the named recipient(s). It
may contain information that is confidential, proprietary or the
subject of legal privilege. This information is not to be used by
any other person and/or organisation. If you are not the intended
recipient, please advise us immediately and delete this e-mail
from your system. Do not use any information contained in it.


For more information on the Television New Zealand Group, visit
us online at http://www.tvnz.co.nz

RE: StaticBucketMap, Re: DO NOT REPLY [Bug 30148] - Internal serverError

[Antonio Gallardo]

Carsten Ziegeler dijo:
>
>
>> -Original Message-
>> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, August 10, 2004 5:49 PM
>> To: [EMAIL PROTECTED]
>> Subject: StaticBucketMap, Re: DO NOT REPLY [Bug 30148] -
>> Internal serverError
>>
>> [EMAIL PROTECTED] wrote:
>> > .
>> >
>> > --- Additional Comments From [EMAIL PROTECTED]
>> > 2004-08-10 11:01 --- The bug was fixed in 2.1.4. Carsten kindly
>> > replaced any reference to the StaticBucketMap with a synchronized
>> > HashMap (not nice, but it works). This was done in the Excalibur
>> > ComponentManager package. Commons-Collections still has the
>> non-threadsafe StaticBucketMap in it.
>>
>> I took a looong look at the current version of
>> StaticBucketMap [1] but fail to see how it is not thread
>> safe... Can anybody give a guess, what can go wrong in this code?
>>
> I can't :( I looked as well through this code and didn't find anything.
> But there must be something, as not only Lars but several others had
> problems with this map under heavy load. Making the map synchronized
> fixed the problem in all cases.

Can you please report it to the commons-collectiosn guys?

Best Regards,

Antonio Gallardo
>
> Carsten
>

RE: StaticBucketMap, Re: DO NOT REPLY [Bug 30148] - Internal serverError

[Carsten Ziegeler]

 

> -Original Message-
> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, August 10, 2004 5:49 PM
> To: [EMAIL PROTECTED]
> Subject: StaticBucketMap, Re: DO NOT REPLY [Bug 30148] - 
> Internal serverError
> 
> [EMAIL PROTECTED] wrote:
> > .
> > 
> > --- Additional Comments From [EMAIL PROTECTED]  
> > 2004-08-10 11:01 --- The bug was fixed in 2.1.4. Carsten kindly 
> > replaced any reference to the StaticBucketMap with a synchronized 
> > HashMap (not nice, but it works). This was done in the Excalibur 
> > ComponentManager package. Commons-Collections still has the 
> non-threadsafe StaticBucketMap in it.
> 
> I took a looong look at the current version of 
> StaticBucketMap [1] but fail to see how it is not thread 
> safe... Can anybody give a guess, what can go wrong in this code?
> 
I can't :( I looked as well through this code and didn't find anything.
But there must be something, as not only Lars but several others had
problems with this map under heavy load. Making the map synchronized
fixed the problem in all cases.

Carsten