I had some more time to play with this; it seems to be related to retiring
old threads, not actual problem on the home server. Some new observations
below.
Alan DeKok wrote on Aug28, 2012:
Brian Julin wrote:
I'm currently hunting a problem that causes a recent checkout of FR3.0
to abort
Brian Julin wrote:
After collecting some more debug logs, I noticed that this problem was
happening too often
on requests numbered around 260 to be a coincidence. It turns out this
happens after
a thread is marked for recycling due to having handled over 128 requests.
Well, set
On 20/09/12 15:29, Alan DeKok wrote:
Brian Julin wrote:
After collecting some more debug logs, I noticed that this problem was
happening too often
on requests numbered around 260 to be a coincidence. It turns out this happens
after
a thread is marked for recycling due to having handled over
I'm currently hunting a problem that causes a recent checkout of FR3.0
to abort but which does not seem to be affecting an older revision (April 8th
or so)
of FR3.0 on another box. I do have a couple small in-house patches applied
but they should probably not be relevant.
The issue seems to
Brian Julin wrote:
I'm currently hunting a problem that causes a recent checkout of FR3.0
to abort but which does not seem to be affecting an older revision
(April 8th or so)
of FR3.0 on another box. I do have a couple small in-house patches applied
but they should probably not be relevant.
5 matches
Mail list logo
