Java, JDBC connection pool, JDBC connection rollback -
we have database connection pool (java jdbc). every time checkout, first preemptive connection rollback avoid connection exceptions. please ignore business case. technical point of view, jdbc connection roll influence application performance lot (since our application mili-second business)?
i dont understand why connections coming directly connection pool need rolled back. state has idle otherwise wouldn't able obtain them pool?!
transactions have influence performance. if there transactions can rolled back, there may query cannot executed because dangling transaction blocking them.
so if application time critical - should invest time optimizing code. use transactions have to.
Comments
Post a Comment