db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2097) Requesting a way (API call?) to test an existing embedded XA connection to determine if the connection is idle and available for reuse by the connection pool.
Date Mon, 11 Dec 2006 21:26:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2097?page=all ]

Stan Bradbury closed DERBY-2097.
--------------------------------

    Resolution: Cannot Reproduce

Can't reproduce this and won't be spending the time needed to define the need generically.
 Also, as commented on, this may not be appropriate functionality to have in a non-debug version
of Derby.

> Requesting a way (API call?) to test an existing embedded XA connection to determine
if the connection is idle and available for reuse by the connection pool.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2097
>                 URL: http://issues.apache.org/jira/browse/DERBY-2097
>             Project: Derby
>          Issue Type: New Feature
>          Components: JDBC
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.6, 10.1.2.1, 10.1.3.1
>            Reporter: Stan Bradbury
>            Priority: Minor
>
> Requesting a way (an API call?) to test an XA datasource connection to determine if the
connection is idle (no outstanding transactions).  This would be used for management of an
XA connection pool.  The test would be performed on a connection before it is returned to
the pool as available for reuse.   This would prevent the failure (XAER_OUTSIDE) seen when
an active connection is incorrectly marked as available and then reallocated for use in a
new transaction (XA_START).
> In this case the front end exception presented is:
> XAException occurred.  Error code is: XAER_OUTSIDE (-9)
> The stack trace produced is:
> 	javax.transaction.xa.XAException
> 	com.ibm.db2j.jdbc.DB2jXAConnection.start
> 	    ....XaResource.start

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

        

Mime
View raw message