[
https://issues.apache.org/jira/browse/FTPSERVER-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Kress updated FTPSERVER-453:
--------------------------------
Attachment: DbUserManager.java
I've added my changes to the class. This passes the unit tests and has resolved
the issue with abandoned db connections.
> pooled db connections not being closed
> --------------------------------------
>
> Key: FTPSERVER-453
> URL: https://issues.apache.org/jira/browse/FTPSERVER-453
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.6
> Environment: ftpserver running in Tomcat on Windows and Linux using a
> JNDI datasource
> Reporter: Ken Kress
> Priority: Minor
> Attachments: DbUserManager.java
>
>
> I set maxActive to 10 and started getting errors while testing. The log
> showed that I was running out of connections, which lead me to believe the
> connections were not being closed. I could not find a problem in the source
> code, but as I played around with it I inadvertently created a new problem
> ... I double closed a connection in DbUserManager.selectUserByName and got
> errors from DbUserManager.authenticate. Researching this new problem, I found
> a solution to both:
> http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html#Random_Connection_Closed_Exceptions.
> I'm not sure why this applies, but I no longer have abandoned connections
> being reclaimed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
