On 06/01/2011 09:08 AM, Kartik Subbarao wrote:
Update: It's not a locks issue.
Another update -- after I reduced the idletimeout to 60 seconds, the
problem seems to have gone away. It would still be useful to know what
might be causing this problem and to be able to support higher levels of
idletimeout, but at least I have another workable option now.
-Kartik