Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1011 Improve Network Server Exception Handling
  3. DERBY-1456

Network Server agentError calls log only to console and are hard to diagnose

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: 10.1.3.2, 10.2.1.6
    • Component/s: Network Server
    • Labels:
      None

      Description

      The Network Server code uses an assertion-check utility routine called agentError()
      under certain circumstances. When these agentError() calls arise, for example as
      in DERBY-1454, there is no server side logging of the error except to the console.

      The user application that hit DERBY-1454 had not been capturing console output and there
      was no clue in the derby.log, this made the problem hard to track down when they
      suddenly hit this boundary deep within their stress tests.

      See also DERBY-743 for another issue with Network Server's agentError routine.

        Attachments

        1. derby1456.stat.txt
          0.1 kB
          Sunitha Kambhampati
        2. derby1456.diff.txt
          3 kB
          Sunitha Kambhampati
        3. 1456_notes.txt
          6 kB
          Sunitha Kambhampati

          Activity

            People

            • Assignee:
              skambha Sunitha Kambhampati
              Reporter:
              bryanpendleton Bryan Pendleton
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: