Glad to hear the bug is fixed!
Would that be responsible for the odd delay? Is the delay caused by some sort of after the fact cache updating?
If the cache is being updated after the fact, then what guarantees that even if this bug is fixed that the cache will be updated instantaneously in the current transaction? From what I can see, a new thread is spawned to update the cache, and it's a race condition? maybe? to see if the cache is updated before the next find() call.
Thanks for your help!
Laird
[Message sent by forum member 'ljnelson' (ljnelson)]
http://forums.java.net/jive/thread.jspa?messageID=228429