Github user bitstorm commented on the issue:
https://github.com/apache/wicket/pull/233
> We don't care about concurrent calls to valueUnbound, that's fine. All
code in that method is thread safe.
I agree
> What we don't want is multiple calls to storeTouchedPages and
valueUnbound (session expiry) to interfere with each other. Synchronizing on
the entry will not help as session expiry is probably done from a different
thread.
Yes, synchronizing is meant to prevent problems for multiple invocations of
storeTouchedPages for the same session, valueUnbound is unaffected. The boolean
value should be enough to tell if valueUnbound is invoked as result of session
expiration.
---
