[DBCP-438] Nested connections in a transaction (local) throws null pointer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0, 2.1
• Fix Version/s: 2.1.1

Environment

All (linux, aix, windows)

• Flags: Important
• Assignee: Unassigned
• Reporter: Raihan Kibria
• Created: 30/Apr/15 10:23
• Updated: 16/Jul/16 00:55
• Resolved: 19/Jul/15 23:23

Description

In a transaction context, if we open multiple connections and close each of them after commit, we get a null pointer exception. Sample code:
transactionManager.begin();

Connection c1 = null;
Connection c2 = null;

c1 = newConnection();
c2 = newConnection();

transactionManager.commit();

try

{ c1.close(); }

catch(Exception e)

{ e.printStackTrace(); }

try

{ c2.close(); }

catch(Exception e)

{ //throws execption e.printStackTrace(); }

Null pointer is thrown at:
org.apache.commons.dbcp2.DelegatingConnection.closeInternal

Affects versions-- 2.1, 2.0