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

["Phil Steitz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DBCP-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522732#comment-14522732 ] 

Phil Steitz commented on DBCP-438:
----------------------------------

Thanks for reporting this and extra thanks for the test case.  I think the problem is likely in the updateTransactionStatus method in ManagedConnection.  

> Nested connections in a transaction (local) throws null pointer
> ---------------------------------------------------------------
>
>                 Key: DBCP-438
>                 URL: https://issues.apache.org/jira/browse/DBCP-438
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: All (linux, aix, windows)
>            Reporter: Raihan Kibria
>         Attachments: TestManagedDataSourceInNesetedConnTx.java, dbcpNull.png
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)