This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
I use Spring 2.5.6 + Hibernate 3.2.GA to implement the application.
And I use the declared transaction in spring , configuration as below
Because I must control the information should be saved when System occurs exception, so I should declare some action to PROPAGATION_REQUIRES_NEW. When I execute the performance , it always show the exception as below
Because the transaction is controlled by Spring, I didn't how to check whether it will release the connection after the transaction complete.
Can someone tell me how to resolve the connection leak problem/
The problem does not seem to be of leaking connections, from what you have posted it seems like the Spring is not able to get connections while trying to start the transaction.
I don't think that the problem is with Spring not releasing connections, Spring aquires a connection on start of transaction releases it back on completion of transaction.
You are using DriverManagerDataSource, which actually does not pool connections, it creates connections on demand.
In case you are running in J2EE container you should look up datasource via JNDI or if you are not running application in container consider using Apache's Jakarta
Commons DBCP or C3P0 connection pool implementations.