[ 
https://issues.apache.org/jira/browse/LOG4NET-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664327#action_12664327
 ] 

Ron Grabowski commented on LOG4NET-192:
---------------------------------------

By more information I meant things like posting your log4net.config file, not 
your configuration file to your application. What appenders are you using? 
FileAppender, MemoryAppender, etc.?

 <log4net>
   <appender name="FileAppender" type="log4net.Appender.FileAppender">
   </appender>    
   <logger name="NHibernate" additivity="false">
     <level value="WARN" />
     <appender-ref ref="FileAppender" />
   </logger>
 </log4net>

How are you configuring log4net?

 XmlConfigurator.ConfigureAndWatch(
  new FileInfo(AppDomain.CurrentDomain.SetupInformation.ApplicationBase + 
"log4net.config"));

Are you sure you're calling that configuring code just one time and not over 
and over?

What kind of multi-threading are you using? Are you creating 1,000 background 
threads to do some of long running processing? What are all these threads 
doing? Are you trying to create a single massive log message and log that?

Do you have a normal .NET stack trace showing where the out of memory exception 
came from? i.e. what method in log4net caused that exception?

Is this your first time using log4net? Did you recently add log4net to your 
application?

> Memory leaks with large multi-threaded application in log4net DLL 1.2.0.30714
> -----------------------------------------------------------------------------
>
>                 Key: LOG4NET-192
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-192
>             Project: Log4net
>          Issue Type: Bug
>         Environment: Windows 2003, .NET framework 1.1
>            Reporter: Vibha Kapur
>            Priority: Critical
>
> We've coded log4net (1.2.0-beta8) into our application. With log4net enabled 
> we see our virtual memory increasing and never decreasing, over a period of 
> time and particularly with stress testing the server runs out of memory and 
> everything grinds to a halt.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to