[ARIES-1542] Aries transaction manager fails with background connection validation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: transaction-jdbc-2.1.2
• Component/s: Transaction
• Assignee: Guillaume Nodet
• Reporter: John Poth
• Created: 02/May/16 13:08
• Updated: 19/Dec/19 17:36
• Resolved: 02/May/16 13:37

Description

This seems to be a defect in org.apache.aries.transaction.jdbc.internal.ValidatingGenericConnectionManager, reflection should be called on the "current" field, not stack. This can cause the following exception:

Caused by: java.lang.RuntimeException: java.lang.NoSuchFieldException: pool
at org.apache.aries.transaction.jdbc.internal.Reflections.get(Reflections.java:56)
at org.apache.aries.transaction.jdbc.internal.ValidatingGenericConnectionManager.<init>(ValidatingGenericConnectionManager.java:89)
at org.apache.aries.transaction.jdbc.internal.ConnectionManagerFactory.init(ConnectionManagerFactory.java:152)
at org.apache.aries.transaction.jdbc.RecoverableDataSource.start(RecoverableDataSource.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)

Issue Links

• relates to: KARAF-4592 Cleanup Aries JDBC Transaction 2.1.2 from the pom.xml