Log4Net, ThreadContext и Global.asax

Question

Log4Net, ThreadContext и Global.asax

Таким образом, мы не должны блокировать очередь только, чтобы узнать, что это было пусто.

object item;
if (queue.Count > 0)
{
  lock (queue)
  {
    if (queue.Count > 0)
    {
       item = queue.Dequeue();
    }
  }
}

5

asp.net vb.net logging error-handling log4net

задан mai 8 March 2017 в 15:00

1 ответ

Другие вопросы по тегам:

asp.net vb.net logging error-handling log4net

Похожие вопросы:

score 11 · Accepted Answer

It is not safe to load request-specific values into ThreadContext like that. The reason is that ASP.NET shared threads to service requests. It does this quite often, in fact.

You could instead use LogicalThreadContext, however that simply stores the values in Call Context, which is used for Remoting.

AFAIK there is no HttpContext specific context storage, so what you can do is instead assign a "value provider" instance as your thread context, and at runtime it will call .ToString() on this class to get the value.

public class HttpContextUserProvider
{
   public override string ToString()
   {
      return HttpContext.Current.User.Identity.Name;
   }
}

It's less than ideal, but it works.