You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Simon Poulter (JIRA)" <ji...@apache.org> on 2007/09/28 15:30:51 UTC
[jira] Created: (LOG4NET-122) Log4Net Not logging
Log4Net Not logging
-------------------
Key: LOG4NET-122
URL: https://issues.apache.org/jira/browse/LOG4NET-122
Project: Log4net
Issue Type: Bug
Affects Versions: 1.2.10
Environment: Windows Server 2003 + Windows Server 2003 64 Bit
Reporter: Simon Poulter
We have being using Log4Net for at least a year with no problems.
Recently we are experiencing the situation where log4net sometimes logs and other times doesn't!
Log4net gets called within the c# code and creates all the files and folders as laid out in the log4net configuration HOWEVER it doesn't always write the logs out after.
This is happening to log files that have been working fine for aleast a year!
Is this a known issue?
Thanks
Simon
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (LOG4NET-122) Log4Net Not logging
Posted by "Ron Grabowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4NET-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Grabowski resolved LOG4NET-122.
-----------------------------------
Resolution: Invalid
Please post support questions to the mailing list.
> Log4Net Not logging
> -------------------
>
> Key: LOG4NET-122
> URL: https://issues.apache.org/jira/browse/LOG4NET-122
> Project: Log4net
> Issue Type: Bug
> Affects Versions: 1.2.10
> Environment: Windows Server 2003 + Windows Server 2003 64 Bit
> Reporter: Simon Poulter
>
> We have being using Log4Net for at least a year with no problems.
> Recently we are experiencing the situation where log4net sometimes logs and other times doesn't!
> Log4net gets called within the c# code and creates all the files and folders as laid out in the log4net configuration HOWEVER it doesn't always write the logs out after.
> This is happening to log files that have been working fine for aleast a year!
> Is this a known issue?
> Thanks
> Simon
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.