> yes, the solution looks like a great deal in both, performance and
> stability,
> enven though i found out that synchronizing the ResourceEntry entry is
> enough. (at least it does not cause my good old error :-)

Most likely itwould be enough, since the sync block in findResourceInternal
made sure that all threads ended up with the same Entry instance. So syncing
on that object should be enough.

I'll commit the change. If there's a problem, let me know.

> i think the concurrent access to the ResourceEntry-object is the point
which
> leads to the error.
> (but i'm not sure if changing synchronized (this) to synchronized (entry)
> will have any signficant positive impact on the performance...)

Essentially, that should allow concurrent CL on different classes, which was
the goal (although it won't have any impact in the real world performance).

> keep on the good work!


I'll try to :)

Remy

Reply via email to