db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julius Stroffek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2432) Implement a transaction time out for XA transactions
Date Fri, 09 Mar 2007 16:15:09 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479634
] 

Julius Stroffek commented on DERBY-2432:
----------------------------------------

There is a commented code in NetXAResource.setTransactionTimeout which contains a call to
non-existing method xaSetTransTimeOut. Anybody knows the origin of this code? Why it is still
there?

the function code is:
---
    public boolean setTransactionTimeout(int seconds) throws XAException {
        if (conn_.agent_.loggingEnabled()) {
            conn_.agent_.logWriter_.traceExit(this, "setTransactionTimeout", false);
        }
        exceptionsOnXA = null;
        return false; // we don't support transaction timeout in our layer.
        /* int rc = xaSetTransTimeOut(seconds);
           if (rc != XAResource.XA_OK)
             throwXAException(rc); */
    }



> Implement a transaction time out for XA transactions
> ----------------------------------------------------
>
>                 Key: DERBY-2432
>                 URL: https://issues.apache.org/jira/browse/DERBY-2432
>             Project: Derby
>          Issue Type: New Feature
>          Components: JDBC
>            Reporter: Julius Stroffek
>
> The XAResource interface provides function setTransactionTimeout which is currently not
supported in derby.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message