jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-463) Uncommitted changes or connection leak with Container Managed Transactions
Date Sat, 16 Sep 2006 12:41:23 GMT
    [ http://issues.apache.org/jira/browse/JCR-463?page=comments#action_12435217 ] 
Jukka Zitting commented on JCR-463:

Do you think this should be included in Jackrabbit 1.1? Some notes:

1) TransactionBoundXAResource.java doesn't have the standard license header.

2) Is this backwards compatible or were previous versions just unusable due to the reported
issue? If no, should the default value of the configuration option be false, at least for

> Uncommitted changes or connection leak with Container Managed Transactions
> --------------------------------------------------------------------------
>                 Key: JCR-463
>                 URL: http://issues.apache.org/jira/browse/JCR-463
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jca
>    Affects Versions: 1.0, 1.0.1
>            Reporter: Edgar Poce
>             Fix For: 1.1
>         Attachments: jca-bintToTransaction.diff
> Apparently the connector doesn't support CMT (container managed transactions). if the
jcr session is closed inside a CMT the AS (application server) throws an exception on commit.
And if the jcr session is leaved open, the AS commits the TX successfully but it causes a
connection leak by leaving the session open.

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


View raw message