I am also experiencing this issue. If an application starts and stops within a JVM, the session pool stays open, even though the instantiating threads have stopped. By staying open the session pool does not release the database (using postgres) connections.
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
I am also experiencing this issue. If an application starts and stops within a JVM, the session pool stays open, even though the instantiating threads have stopped. By staying open the session pool does not release the database (using postgres) connections.
I generally see two threads, one of which is:
Daemon Thread com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1