Will the connection pool close off statements/preparedStatements/callableStatements when I close/release the connection?
As of v0.6.4 onwards, no, though it will issue warnings if you forget to do so (with the right config settings enabled). This ensures that during development you can fix all the relevant bugs whilst not affecting general performance. However the JDBC spec is very unclear on the expected behaviour of what should happen when a connection is closed so always make sure to close off the statements you are done with manually yourself anyway. Consider how your application would behave if in future you need to change to a different connection pool for example.
Related Questions
- What is the connection between language and resonance? Why does HR muscle check the body s resonance by using verbal statements and phrases?
- Will the connection pool close off statements/preparedStatements/callableStatements when I close/release the connection?
- Connections per user or Connection Pool – Which is recommended?
