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, 14 Jun 2007 15:16:26 GMT

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


Mime
View raw message