On 06/01/2011 12:19 PM, Kartik Subbarao wrote:
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.
Well it looks like I spoke somewhat too soon. The problem hasn't
entirely gone away, but now it happens less frequently, and only hangs
for 60 seconds instead of 20 minutes. Which confirms my observation that
this is idletimeout-related. Any thoughts/ideas would be greatly