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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/06/30 20:16:20 UTC

[jira] [Updated] (DERBY-4163) It would be good if Derby could raise connectionErrorOccurred on pooled connections when the database is shutdown

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

Mamta A. Satoor updated DERBY-4163:
-----------------------------------

    Urgency: Low
     Labels: derby_triage10_11  (was: )
    
> It would be good if Derby could raise  connectionErrorOccurred on pooled connections when the database is shutdown
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4163
>                 URL: https://issues.apache.org/jira/browse/DERBY-4163
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.6.1.0
>            Reporter: Kathey Marsden
>            Priority: Minor
>              Labels: derby_triage10_11
>         Attachments: TestShutdownEvents.zip
>
>
> It would be good if on shutdown of the database, pooled connections were invalidated by calling connectionErrorOccurred if a listener is registered.  See the attached program TestShutdownEvents to see that no call is made to connectionErrorOccurred on shutdown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira