You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Julius Stroffek (JIRA)" <ji...@apache.org> on 2007/03/08 16:16:24 UTC
[jira] Created: (DERBY-2421) implement the finalize method
separately for both client and network drivers.
implement the finalize method separately 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
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.
[jira] Updated: (DERBY-2421) implement the finalize method
separately (currently, the close method is called) for both client and
network drivers.
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julius Stroffek updated DERBY-2421:
-----------------------------------
Summary: implement the finalize method separately (currently, the close method is called) for both client and network drivers. (was: implement the finalize method separately for both client and network drivers.)
> 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.
[jira] Assigned: (DERBY-2421) implement the finalize method
separately for both client and network drivers.
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julius Stroffek reassigned DERBY-2421:
--------------------------------------
Assignee: Julius Stroffek
> implement the finalize method separately 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.
[jira] Commented: (DERBY-2421) implement the finalize method
separately (currently, the close method is called) for both client and
network drivers.
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504771 ]
Julius Stroffek commented on DERBY-2421:
----------------------------------------
If the client connects to network server this issue is/might be handled by DERBY-2220 and DERBY-2432. For embedded driver this issue just affects the wrong application itself not the database where other users can connect.
Since the above and considering that it is not a good practice to do more complex things in finalize method, I think we can close this sub-task with "Won't Fix". If nobody objects I will do that in couple of days.
> 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
> Components: Network Client, Network Server
> Reporter: Julius Stroffek
> Assignee: 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.
[jira] Commented: (DERBY-2421) implement the finalize method
separately (currently, the close method is called) for both client and
network drivers.
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-2421) implement the finalize method
separately (currently, the close method is called) for both client and
network drivers.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2421:
----------------------------------
Component/s: Network Server
Network Client
> 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
> Components: Network Client, Network Server
> 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.
[jira] Closed: (DERBY-2421) implement the finalize method
separately (currently, the close method is called) for both client and
network drivers.
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julius Stroffek closed DERBY-2421.
----------------------------------
Resolution: Won't Fix
> 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
> Components: Network Client, Network Server
> Reporter: Julius Stroffek
> Assignee: 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.