I agree. There is no problem with the close method of ResilientFileOutputStream. The FileAppenders I stop in my application are nested in a SiftingAppender. When those FileAppenders are stopped the underlying streams are closed, but instances of FileAppender, ResilientFileOutputStream, etc. are kept in memory since FileAppenders are still in the map managed by the AppenderTracker. I solved this problem using the method stopAndRemoveNow of AppenderTracker instead of the stop method of FileAppender.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira