[jboss-jira] [JBoss JIRA] Assigned: (JBAS-3770) JBoss/JCA JDBC implementation should allow for Transaction isolation level to be reset on underlying JDBC connection prior to return to pool

[Vicky Kak (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3770?page=all ]

Vicky Kak reassigned JBAS-3770:
-------------------------------

    Assignee: Vicky Kak  (was: Weston Price)

> JBoss/JCA JDBC implementation should allow for Transaction isolation level to be reset on underlying JDBC connection prior to return to pool
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-3770
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3770
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>            Reporter: Weston Price
>         Assigned To: Vicky Kak
>            Priority: Minor
>
> By default, when we return a JDBC connection to the pool we execute the following in the ManagedConnection.cleanup() method: 
> if (jdbcTransactionIsolation != transactionIsolation)
>          {
>             try
>             {
>                con.setTransactionIsolation(jdbcTransactionIsolation);
>                jdbcTransactionIsolation = transactionIsolation;
>             }
>             catch (SQLException e)
>             {
>                mcf.log.warn("Error resetting transaction isolation ", e);
>             }
> }
> In this scenario we don't return the original isolation level on the underlying connection. The spec doesn't prohibit this, and I can't see any reason why we shouldn't do this, or provide a configurable option. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira