log4net: dismember exception

Question

I want to separate exception's stack trace from their message. for instance in this example:

System.NullReferenceException: Object reference not set to an instance of an object.
at BettweenSvc.Bettweensvc.processRequest(RequestManagerRepository rmr, RequestConversation rc) in C:\Repository\bettween\trunk\Solution\BettweenSvc\Bettweensvc.cs:line 277
at BettweenSvc.Bettweensvc.bettweenTimer_Elapsed(Object sender, ElapsedEventArgs e) in C:\Repository\bettween\trunk\Solution\BettweenSvc\Bettweensvc.cs:line 111

I want to log

System.NullReferenceException: Object reference not set to an instance of an object.

in one field and the rest in another

Currently I have

<parameter>
  <parameterName value="@exception" />
  <dbType value="String" />
  <size value="2000" />
  <layout type="log4net.Layout.ExceptionLayout" />
</parameter>

in my AdoNetAppender, how would I do this?

You cruel man - poor exception :( – Oded Aug 04 '11 at 18:52 — Oded, Aug 04 '11 at 18:52
I couldn't come up with a better name :( – bevacqua Aug 04 '11 at 18:54 — bevacqua, Aug 04 '11 at 18:54

score 2 · Accepted Answer · edited May 23 '17 at 12:19

2

This should work:

<parameter>
  <parameterName value="@exception" />
  <dbType value="String" />
  <size value="2000" />
  <layout type="log4net.Layout.PatternLayout">
    <conversionPattern value="%exception{message}" />
  </layout>
</parameter>

If you want the stacktrace you use %exception{stacktrace}.

EDIT:
If you are using log4net 1.2.10 then you need to implement your own pattern layout that does what you want. I recommend to check the current log4net source code (trunk) to see how they do it (it is quite simple really). Here is an example of such a layout converter.

edited May 23 '17 at 12:19

Community

1
1

answered Aug 05 '11 at 10:12

Stefan Egli

17,398
3
54
75

That doesn't work, it just outputs the same as `log4net.Layout.ExceptionLayout`. – bevacqua Aug 05 '11 at 13:54
Are you really using PatternLayout instead of ExceptionLayout? I just tested it and it works as expected. – Stefan Egli Aug 05 '11 at 14:33
Ok, maybe this feature is implemented in the last revision of log4net (that is not published). I will check if the feature was already implemented in 1.2.10 – Stefan Egli Aug 05 '11 at 14:42
This feature is indeed not in 1.2.10 – Stefan Egli Aug 05 '11 at 14:46

log4net: dismember exception

1 Answers1