Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.0.9, 1.0.13, 1.1.3
-
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.
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.
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.
