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 "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/02/11 20:22:28 UTC
[jira] Created: (DERBY-958) Network Client should not print
non-ascii token separators in message for NullPointerExceptions or other
serious non SQLExceptions
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
Type: Bug
Components: Network Client
Versions: 10.1.2.2, 10.2.0.0, 10.1.3.0, 10.1.2.3
Reporter: Kathey Marsden
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
[jira] Updated: (DERBY-958) Network Client should not print
non-ascii token separators in message for NullPointerExceptions or other
serious non SQLExceptions
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-958?page=all ]
Kathey Marsden updated DERBY-958:
---------------------------------
Urgency: Normal
Fix Version/s: 10.2.0.0
This is a bothersome bug that comes back to haunt us from time to time so would be good to fix. Especially since cutting and pasting these traces into Jira breaks JIRA export.
> 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.2.2, 10.2.0.0, 10.1.3.0, 10.1.2.3
> Reporter: Kathey Marsden
> Fix For: 10.2.0.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
[jira] Updated: (DERBY-958) Network Client should not print
non-ascii token separators in message for NullPointerExceptions or other
serious non SQLExceptions
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DERBY-958) Network Client should not print
non-ascii token separators in message for NullPointerExceptions or other
serious non SQLExceptions
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-958?page=all ]
Rick Hillegas updated DERBY-958:
--------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.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.2.2, 10.2.1.0, 10.1.3.0, 10.1.2.3
> Reporter: Kathey Marsden
> Fix For: 10.2.2.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