Atomikos Forum

High number of acquired JDBC connections

Hello,

While investigating performance issues, I've come across a difference in acquired JDBC connections. For a transaction in which we execute about 109 queries, Hibernate session metrics reports 108 acquired JDBC connections when configured with Atomikos. When using Spring's Hibernate transaction manager, only 1 acquired connection is reported.

Atomikos:
153609065 nanoseconds spent acquiring 108 JDBC connections;
399422528 nanoseconds spent releasing 108 JDBC connections;
280503938 nanoseconds spent preparing 109 JDBC statements;
295447606 nanoseconds spent executing 109 JDBC statements;

Atomikos logs contain lots of these statements:
14-11-28 13:28:06,462 [http-bio-8080-exec-5] AtomikosDataSoureBean 'AtomikosDataSourceJDBCOracle.DS': getConnection ( null )...

Spring HibernateTransactionManager:
2130360 nanoseconds spent acquiring 1 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
4551614 nanoseconds spent preparing 108 JDBC statements;
286170856 nanoseconds spent executing 108 JDBC statements;

Is this normal behaviour or am I doing something wrong?

The performance issues I referred to were caused by slow database queries, but our application regularly reports connection pool exhaustions as well, which are probably related to those slow queries, but I was wondering if this could be harmful as well?

Thanks in advance for your feedback!

Best regards,
Stijn
Stijn Lambert Send private email
Monday, December 01, 2014
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics