%aspnet-session{key} bug?

[Chris Meeusen]

Hi,

I'm brand new to this list.  I think i have come across a bug in the
way the %aspnet-session conversion pattern is being read from my
config.  It seems that log4net is short circuiting and taking the %a
from %aspnet-session to be the appdomain and not aspnet-session.


Here is a portion of my config:
      <parameter>
        <parameterName value="@session" />
        <dbType value="String" />
        <size value="2147483647"/>
        <layout type="log4net.Layout.PatternLayout">
          <conversionPattern value="%aspnet-session{gwsession}" />
        </layout>
      </parameter>

Here a snippet from log4net debug trace:

log4net: XmlHierarchyConfigurator: Setting Property
[ConversionPattern] to String value [%aspnet-session{gwsession}]
log4net: PatternParser: Converter [a] Option [] Format
[min=-1,max=2147483647,leftAlign=False]
log4net: PatternParser: Converter [literal] Option
[spnet-session{gwsession}] Format
[min=-1,max=2147483647,leftAlign=False]
log4net: XmlHierarchyConfigurator: Setting Property [Layout] to object
[log4net.Layout.Layout2RawLayoutAdapter]
log4net: XmlHierarchyConfigurator: Setting Collection Property
[AddParameter] to object [log4net.Appender.AdoNetAppenderParameter]

Am i using this conversion pattern wrong or is this a bug?

Thanks,
Chris