From: Dominik Psenner
Sent: Monday, May 22, 2017 1:27 PM
>> Please note that it is known that an application can also cause log4net
to deadlock [3].
>> [3] https://issues.apache.org/jira/browse/LOG4NET-298
This particular application is not using any async/task code so not sure if
ot
Dominik,
Thank you for your reply.
>> please don't expect a sensible response within hours, especially with such a
>> complex problem.
No problem, I looked at the archive and noticed I was the only post this month
so was thinking that maybe a newer list existed.
>> :-) At first sight, if
Is this list still active? Would this be better to post to the dev list?
> On May 19, 2017, at 3:45 PM, Jim Scott wrote:
>
> We have a webservice that has been running on Windows 2008R2 since Nov 2015
> and has not had any issues until just a week or so ago. The webservic
We have a webservice that has been running on Windows 2008R2 since Nov 2015 and
has not had any issues until just a week or so ago. The webservice becomes
unresponsive and after installing some debug tools I can see that we have a
deadlock issue.
Here is some details of the last dump. Note we a
try
{
//test
}
catch(Exception ex)
{
log.Error(ex); // log your exception
throw; // allow exception to continue
}
-Original Message-
From: "superfreak3"
Sent: 1/6/2016 6:57 AM
To: "log4net-user@logging.apache.org"
Subject: Re: Using Log4Net with Selenium
I've found t
FYI, here is the enhancements that I suggested back in Jan, 2011 that I was
referring to in my last email.
I have been using the AdoNetAppender for a while now and have a few issues with
it.
1) If the database that it logs to goes offline it will stop logging messages
until the application is
By default the AdoNetAppender will not attempt to reconnect to the database if
it looses its connection for any reason. Take a look at ReconnectOnError
property. Note however that if you set this property to true and your database
is not available every time you attempt to log something to the D
-Original Message-
From: Stefan Bodewig
Sent: Wednesday, August 10, 2011 8:38 AM
I'd propose to not keep the signing key of future releases secret but
simply keep the full keypair inside the source tree.
Stefan
---
I second that!
Jim
From: Johannes Gustafsson
Sent: Monday, August 08, 2011 1:20 PM
To: log4net-user@logging.apache.org
Subject: Compiling log4net with strong name and 3rd party dependencies
Hi,
There are a few bugfixes in the trunk that I need and since there has been no
new release for a very long time, I tried
Try this
type="log4net.Appender.RollingFileAppender">
On 1/13/2011 8:28 PM, cyz wrote:
Hi, I'd like to have a logging system with below behaviors, is
RollingFileAppender able to achieve?
1> messages are logged to a fixed file name, say log.txt.
2> log files are auto backup by si
10 matches
Mail list logo