[ http://issues.apache.org/jira/browse/DERBY-958?page=all ]
Rick Hillegas updated DERBY-958:
--------------------------------
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> Network Client should not print non-ascii token separators in message for
> NullPointerExceptions or other serious non SQLExceptions
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-958
> URL: http://issues.apache.org/jira/browse/DERBY-958
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.1.3.1, 10.2.1.6
> Reporter: Kathey Marsden
> Fix For: 10.2.3.0
>
>
> The bug DERBY-939 showed non-ascii characters in the exception when there was
> a null pointer exception on the server and the client could not retrieve the
> message.
> This issue was fixed in DERBY-285 for serious SQLExceptions but is still a
> problem in the case of the NullPointerException and may also still be a
> problem when retrieveMessageText=fase.
> See DERBY-939 for a repro. See DERBY-285 for more details on the issue.
--
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
