Bug with RollingLogFileAppender? Ordering of appender-refs seems to be important?

I seem to have seen a bug with the RollingLogFileAppender:

If I use the following config, messages DO NOT get written to the logfile
(although the logfile DOES get created):

	<log4net>
		<appender name="RollingLogFileAppender"
type="log4net.Appender.RollingFileAppender">
			<param name="File"
value="c:/logs/notificationbridge.log" />
			<param name="AppendToFile" value="true" />
			<param name="MaxSizeRollBackups" value="10" />
			<param name="MaximumFileSize" value="5MB" />
			<param name="RollingStyle" value="Size" />
			<param name="StaticLogFileName" value="true" />

			<layout type="log4net.Layout.PatternLayout">
				<param name="ConversionPattern" value="%d
[%t] %-5p %c [%x] - %m%n" />
			</layout>
		</appender>
		<appender name="ConsoleAppender"
type="log4net.Appender.ConsoleAppender">
			<layout type="log4net.Layout.PatternLayout">
				<param name="ConversionPattern" value="%d
[%t] %-5p %c [%x] - %m%n" />
			</layout>
		</appender>

		<!-- Setup the root category, add the appenders and set the
default priority -->
		<root>
			<priority value="ALL" />
			<appender-ref ref="RollingLogFileAppender" />
			<appender-ref ref="ConsoleAppender" />
		</root>

	</log4net>

However, if I swap the ordering of the Appender-refs:

			<appender-ref ref="ConsoleAppender" />
			<appender-ref ref="RollingLogFileAppender" />

Then messages DO get written to the logfile.

I am using log4net1.1, with NUnit 2.1 on .Net 1.1

I've asked before, but got no answer:  when is 1.2 going to exit "beta"
status (when will 1.2 be an offical release?).  Is anyone actively
developing/maintaining log4net?

Pete


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com