[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#3746) Lock table errors

quanah@symas.com wrote:

>but that is not associated with any connection ID, making finding the error 
>on a busy system less than easy.
>So, is it possible to get the syslog output at least tied to the connection 
>that created it, so that its easy to find? :)
Like I said, none of the caller's context is available since that error 
is logged in a BDB callback. So there's no way to know the connection ID 
at that point. Nor do I think it is particularly worthwhile to make such 
an association. Generally when an internal error occurs, something has 
gone so wrong that requests will start to fail regardless of the session.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support