db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1891) error 58009.C.19 refers to non-existent codepoint secktn - needs correcting
Date Thu, 28 Sep 2006 05:58:51 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1891?page=all ]

Andrew McIntyre resolved DERBY-1891.
------------------------------------

    Fix Version/s: 10.2.2.0
       Resolution: Fixed

Merged to 10.2 branch with revision 450713 (code) and revision 450712 (docs).

> error 58009.C.19  refers to non-existent codepoint secktn - needs correcting
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-1891
>                 URL: http://issues.apache.org/jira/browse/DERBY-1891
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.0.2.1, 10.3.0.0
>            Reporter: Myrna van Lunteren
>         Assigned To: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.2.2.0, 10.3.0.0
>
>         Attachments: DERBY-1891_doctr_20060926.diff, DERBY-1891_tr_20060926.diff
>
>
> error 58009.C.19=Network protocol exception: secktn was not returned.  The connection
has been terminated.
> This is NET_SECTKN_NOT_RETURNED in org.apache.derby.drda.client.net.NetConnection.java
> I searched in the drda specs but I could not find SECKTN, but I *did* find SECTKN.
> So...I think the error message should get changed to SECTKN.
> The same non-existent codepoint seems to be referred to in: XN002.U=secktn was not returned.
> This affects the following:
> - English messages .properties file(s)
> - Brazilian messages .properties file(s)
> - documentation for SQLStates.
> I didn't find any masters with this.
> It should probably go into 10.2.1, although it's not important enough to hold up a release.
Targeting for 10.2.2 for now.
> Myrna

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message