Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-958

Network Client should not print non-ascii token separators in message for NullPointerExceptions or other serious non SQLExceptions

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.1.3.1, 10.2.1.6
    • Fix Version/s: None
    • Component/s: Network Client
    • Urgency:
      Normal

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kmarsden Kathey Marsden
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: