[Not relevant here, but might be an idea to make
private boolean scanUntilRemovable;
final to avoid any untoward behaviour.]
Not sure if this is relevant, but the super-class AbstractHashedMap is
not thread-safe.
For example, the instance variable "size" is not protected against
multiple threads: the field size is not volatile, and it is not
accessed via synchronised methods.
Might be an idea to document which classes are intended to be thread-safe?
Also might be worth running the code against FindBugs in case that
gives more clues. I can perhaps do that tonight.
HTH.
Seb
On 10/10/05, Phil Steitz <[EMAIL PROTECTED]> wrote:
> Still nothing meaningful to report, other than that it is easy to get
> the NPE when access to put / get is not synchronized. I do not see
> how this could happen, though when access is synchronized and the keys
> are immutable. Will keep trying.
>
> Stephen - can you pls attach the debug source to the ticket? thx
>
> Phil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
