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-2421) implement the finalize method separately (currently, the close method is called) for both client and network drivers.
Date Thu, 08 Mar 2007 16:54:24 GMT

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

Julius Stroffek commented on DERBY-2421:
----------------------------------------

If the XAConnection object is going to be garbage collected, I think It is quite safe to rollback
the global transaction associated with the connection. Otherwise, the locks held by the transaction
will not be released later. I think, this is not covered by the JTA spec and also not by "Distribute
Transaction Processing: XA Specification". I also can not see a much sense in making a difference
in behavior between embedded and network driver - so I would do the same for both.

Please correct me if I am wrong. Any other opinions?

> implement the finalize method separately (currently, the close method is called) for
both client and network drivers.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2421
>                 URL: https://issues.apache.org/jira/browse/DERBY-2421
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Julius Stroffek
>         Assigned To: Julius Stroffek
>
> If the garbage collection will be performed on XAConnection objects the correct cleanup
have to be performed and also the roll-back of the whole global transaction should be considered
and discussed here.

-- 
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