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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/07/13 20:45:15 UTC

[jira] Closed: (DERBY-4165) Document the effect of shutdown on in progress transactions and open connections.

     [ https://issues.apache.org/jira/browse/DERBY-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden closed DERBY-4165.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 10.6.0.0
                   10.5.1.2

Committed revision 793658 to 10.5. I don't plan to backport further.


> Document the effect of shutdown on in progress transactions and open connections.
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-4165
>                 URL: https://issues.apache.org/jira/browse/DERBY-4165
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.6.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>             Fix For: 10.5.1.2, 10.6.0.0
>
>         Attachments: derby-4165_diff.txt, derby-4165_diff.txt, tdevdvlp40464.html, tdevdvlp40464.html
>
>
> I have noticed if the database is shutdown various operations on open connections can cause NullPointerExceptions, assertion failures and other issues.  The documentation should recommend that existing open connections be closed before shutting down the database or the engine and that unexpected behavior may occur if connections are reused after shutdown.

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