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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/02/06 19:26:09 UTC

[jira] [Resolved] (DERBY-6426) Fix isLoginException

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

Myrna van Lunteren resolved DERBY-6426.
---------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 10.1.3.2)
                   10.11.0.0
                   10.10.1.4
                   10.9.2.2
                   10.8.3.3

Merged the change cleanly to all branches where the no-op code existed.
Resolving.
Thanks for the contribution Dave.

> Fix isLoginException
> --------------------
>
>                 Key: DERBY-6426
>                 URL: https://issues.apache.org/jira/browse/DERBY-6426
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.9.1.0
>            Reporter: Dave Brosius
>            Assignee: Dave Brosius
>            Priority: Trivial
>             Fix For: 10.8.3.3, 10.9.2.2, 10.10.1.4, 10.11.0.0
>
>         Attachments: fix_isLoginException.txt
>
>
> code treats any StandardException as a login exception due to curious no-op code. Added login state check to make it work as expected.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)