JDBC support in V3 Prelude
By shalini_m on Nov 06, 2008
Some of the cool features that could be useful to you are :
- Connection Leak Tracing
- enable the connection-leak-timeout to a certain value along with connection-leak-reclaim to true to avoid the potential connection leaks in your application
- Validation calls optimization
- Set the validate atmost once period to a value within which the validation will be carried out atmost once.
- Associate with thread
- To reuse connections in a multi threaded application to avoid the overhead of getting a connection from the pool.
and many more...
Things that have changed:
Setting the pool properties/attributes using asadmin set command would be like:
asadmin set --value=10 server.resources.jdbc-connection-pool.DerbyPool.steady-pool-size
asadmin set --value=newUser server.resources.jdbc-connection-pool.DerbyPool.property.User
Note that the first asadmin set does not need a server restart whereas the second one mandates restart.
There are many more attractive things coming up in the next release of V3 for JDBC. One of them is advanced pool monitoring. The monitoring framework has undergone a major change in v3 prelude.
Try the latest V3 prelude and its connection pooling features. Any issues? Mail users-AT-glassfish.dev.java-DOT-net .