You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-user@logging.apache.org by Steve Hueners <am...@gmail.com> on 2014/08/18 22:07:50 UTC
AdoNetAppender on Azure SQL: Works then quits working
Last week I stepped thru the hoops required to configure a connection
string for my Azure SQL db and confirmed that logging was working as
expected. Log messages were stored for several days, but at some
point, the logging ceased. I re-published the site (without changing
anything related to Log4Net) and logging was again active. Any other
similar reports? Anything non-optimal with my config?
much appreciated!
<appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender">
<bufferSize value="1" />
<connectionType value="System.Data.SqlClient.SqlConnection,
System.Data, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" />
<connectionString
value="Server=tcp:myServer.database.windows.net,1433;Database=myDatabase;User
ID=myUser;Password=myPassword;Trusted_Connection=False;Encrypt=True;Connection
Timeout=30;" />
<commandText value="INSERT INTO CULog
([Date],[Level],[Message],[Exception], Logger) VALUES (@log_date,
@log_level, @message, @exception, @logger)" />
<parameter>
<parameterName value="@log_date" />
<dbType value="DateTime" />
<layout type="log4net.Layout.RawTimeStampLayout" />
</parameter>
<parameter>
<parameterName value="@log_level" />
<dbType value="String" />
<size value="50" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%level" />
</layout>
</parameter>
<parameter>
<parameterName value="@message" />
<dbType value="String" />
<size value="4000" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%message" />
</layout>
</parameter>
<parameter>
<parameterName value="@exception" />
<dbType value="String" />
<size value="4000" />
<layout type="log4net.Layout.ExceptionLayout" />
</parameter>
<parameter>
<parameterName value="@logger" />
<dbType value="String" />
<size value="4000" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%logger" />
</layout>
</parameter>
RE: AdoNetAppender on Azure SQL: Works then quits working
Posted by Joe <jo...@hotmail.com>.
It's in the FAQ: http://logging.apache.org/log4net/release/faq.html
<appSettings>
<add key="log4net.Internal.Debug" value="true"/>
</appSettings>
-----Original Message-----
From: Steve Hueners [mailto:am.steve@gmail.com]
Sent: 18 September 2014 12:12
To: Log4NET User
Subject: Re: AdoNetAppender on Azure SQL: Works then quits working
On Wed, Aug 20, 2014 at 11:01 AM, Joe <Jo...@hotmail.com> wrote:
> and route this trace output to a file.
Thanks much for your reply. I'm not clear about how to route the internal debug output to a trace file. An Azure website provides access to the file system via the project's App_Data so if I knew the precise step/syntax required to 'route this trace to a file' I think I'd be able to produce some output. --appreciated
Re: AdoNetAppender on Azure SQL: Works then quits working
Posted by Steve Hueners <am...@gmail.com>.
On Wed, Aug 20, 2014 at 11:01 AM, Joe <Jo...@hotmail.com> wrote:
> and route this trace output to a file.
Thanks much for your reply. I'm not clear about how to route the
internal debug output to a trace file. An Azure website provides
access to the file system via the project's App_Data so if I knew the
precise step/syntax required to 'route this trace to a file' I think
I'd be able to produce some output. --appreciated
RE: AdoNetAppender on Azure SQL: Works then quits working
Posted by Joe <Jo...@hotmail.com>.
I'd try enabling Log4net tracing (<add key="log4net.Internal.Debug" value="true"/>) and route this trace output to a file.
It might give you a clue as to what's happening - perhaps AdoNetAppender is not recovering from a database connection failure properly.
-----Original Message-----
From: Steve Hueners [mailto:am.steve@gmail.com]
Sent: mardi 19 août 2014 16:34
To: log4net-user@logging.apache.org
Subject: Re: AdoNetAppender on Azure SQL: Works then quits working
It happened again last night - I had a line logged at 2014-08-19
00:59:59.537 (gmt) then nothing until I restarted the website.
On Mon, Aug 18, 2014 at 3:07 PM, Steve Hueners <am...@gmail.com> wrote:
> Last week I stepped thru the hoops required to configure a connection
> string for my Azure SQL db and confirmed that logging was working as
> expected. Log messages were stored for several days, but at some
> point, the logging ceased. I re-published the site (without changing
> anything related to Log4Net) and logging was again active. Any other
> similar reports? Anything non-optimal with my config?
>
> much appreciated!
>
> <appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender">
> <bufferSize value="1" />
> <connectionType value="System.Data.SqlClient.SqlConnection,
> System.Data, Version=4.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089" />
>
> <connectionString
> value="Server=tcp:myServer.database.windows.net,1433;Database=myDataba
> se;User
> ID=myUser;Password=myPassword;Trusted_Connection=False;Encrypt=True;Co
> nnection
> Timeout=30;" />
> <commandText value="INSERT INTO CULog
> ([Date],[Level],[Message],[Exception], Logger) VALUES (@log_date,
> @log_level, @message, @exception, @logger)" />
> <parameter>
> <parameterName value="@log_date" />
> <dbType value="DateTime" />
> <layout type="log4net.Layout.RawTimeStampLayout" />
> </parameter>
> <parameter>
> <parameterName value="@log_level" />
> <dbType value="String" />
> <size value="50" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%level" />
> </layout>
> </parameter>
> <parameter>
> <parameterName value="@message" />
> <dbType value="String" />
> <size value="4000" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%message" />
> </layout>
> </parameter>
>
> <parameter>
> <parameterName value="@exception" />
> <dbType value="String" />
> <size value="4000" />
> <layout type="log4net.Layout.ExceptionLayout" />
> </parameter>
> <parameter>
> <parameterName value="@logger" />
> <dbType value="String" />
> <size value="4000" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%logger" />
> </layout>
> </parameter>
Re: AdoNetAppender on Azure SQL: Works then quits working
Posted by Steve Hueners <am...@gmail.com>.
It happened again last night - I had a line logged at 2014-08-19
00:59:59.537 (gmt) then nothing until I restarted the website.
On Mon, Aug 18, 2014 at 3:07 PM, Steve Hueners <am...@gmail.com> wrote:
> Last week I stepped thru the hoops required to configure a connection
> string for my Azure SQL db and confirmed that logging was working as
> expected. Log messages were stored for several days, but at some
> point, the logging ceased. I re-published the site (without changing
> anything related to Log4Net) and logging was again active. Any other
> similar reports? Anything non-optimal with my config?
>
> much appreciated!
>
> <appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender">
> <bufferSize value="1" />
> <connectionType value="System.Data.SqlClient.SqlConnection,
> System.Data, Version=4.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089" />
>
> <connectionString
> value="Server=tcp:myServer.database.windows.net,1433;Database=myDatabase;User
> ID=myUser;Password=myPassword;Trusted_Connection=False;Encrypt=True;Connection
> Timeout=30;" />
> <commandText value="INSERT INTO CULog
> ([Date],[Level],[Message],[Exception], Logger) VALUES (@log_date,
> @log_level, @message, @exception, @logger)" />
> <parameter>
> <parameterName value="@log_date" />
> <dbType value="DateTime" />
> <layout type="log4net.Layout.RawTimeStampLayout" />
> </parameter>
> <parameter>
> <parameterName value="@log_level" />
> <dbType value="String" />
> <size value="50" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%level" />
> </layout>
> </parameter>
> <parameter>
> <parameterName value="@message" />
> <dbType value="String" />
> <size value="4000" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%message" />
> </layout>
> </parameter>
>
> <parameter>
> <parameterName value="@exception" />
> <dbType value="String" />
> <size value="4000" />
> <layout type="log4net.Layout.ExceptionLayout" />
> </parameter>
> <parameter>
> <parameterName value="@logger" />
> <dbType value="String" />
> <size value="4000" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%logger" />
> </layout>
> </parameter>