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/01/21 19:00:22 UTC

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

    [ https://issues.apache.org/jira/browse/DERBY-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877667#comment-13877667 ] 

Myrna van Lunteren commented on DERBY-6426:
-------------------------------------------

Is this fix getting backported? Is it suitable for backport, or are there risks?
Or can this issue be resolved (for) now?

> 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.1.3.2
>
>         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)