Issue Type: Bug Bug
Affects Versions: 1.1.3, 1.0.13, 1.0.9
Assignee: Logback dev list
Attachments: mem-leak.zip
Components: logback-classic
Created: 02/Aug/15 12:38 PM
Description:

I'm attaching a skeleton web servlet that illustrates the problem. Deploying the project and immediately after that undeploying it, will not cause a memory issue since the logger isn't triggered. If however, you use a browser and navigate to http://localhost:8080/mem-leak/ the application cannot unload since the DBAppender has been invoked.
If you remove the references to DBAppender from logback.xml everything works like a dream no matter what you do.

Environment:

Running a Postgres 9.3 database with the standard logging schema set up and proper user rights, this systematically fails to unload. It's been tried with java 7 and 8. Under Windows, linux, and OS X. And all sorts of tomcat versions and configurations. Currently i'm running with postgresql-9.3-1101-jdbc41.jar installed in tomcat/lib.

Project: logback
Labels: dbappender
Priority: Major Major
Reporter: Søren Turin
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
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev

Reply via email to