If you configure the AMQP appender incorrectly (e.g. change to a non-existent host like , the appender throws an exception that brings down W3WP.exe.
This happens here in GelfAmqpAppender.cs:
protected override void OnClose()
{
Channel.Close();
Channel.Dispose();
Connection.Close();
Connection.Dispose();
}
If you change this code as follows, the problem goes away:
protected override void OnClose()
{
if (Channel != null)
{
Channel.Close();
Channel.Dispose();
}
if (Connection != null)
{
Connection.Close();
Connection.Dispose();
}
}
So, either Channel or Connection are null (not sure which).
Stack traces from the Windows application log, in order, are as follows:
001.txt002.txt003.txt
If you configure the AMQP appender incorrectly (e.g. change to a non-existent host like , the appender throws an exception that brings down W3WP.exe.
This happens here in GelfAmqpAppender.cs: protected override void OnClose() { Channel.Close(); Channel.Dispose(); Connection.Close(); Connection.Dispose(); }
If you change this code as follows, the problem goes away: protected override void OnClose() { if (Channel != null) { Channel.Close(); Channel.Dispose(); } if (Connection != null) { Connection.Close(); Connection.Dispose(); } }
So, either Channel or Connection are null (not sure which).
Stack traces from the Windows application log, in order, are as follows: 001.txt 002.txt 003.txt