Derby
  1. Derby
  2. DERBY-5427

Unauthorized shutdown should not generate thread dump and javacore. AuthenticationTest dumps over 20 javacores with IBM JVM for normal user errors

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.7.1.4
    • Fix Version/s: 10.8.3.0, 10.9.1.0
    • Component/s: Services
    • Labels:
      None
    • Urgency:
      Urgent
    • Issue & fix info:
      High Value Fix, Patch Available, Repro attached, Workaround attached
    • Bug behavior facts:
      Regression

      Description

      If jdbcapi.AuthenticationTest is run without changing the derby.stream.error.extendedDiagSeverityLevel as is done in the test, it generates thread dumps and javacores for IBM jvms. I beleive the errors in this test are expected user errors and not crashes so they should not generate a thread dump or javacore. To reproduce remove this line from test:

      //Derby-4856,set the property to avoid thread dump and diagnostic info
      sysprops.put("derby.stream.error.extendedDiagSeverityLevel","50000");

      Until fixed, users can work around the issue by setting derby.stream.error.extendedDiagSeverityLevel to 50000 as is done in the test.

      1. derby-5427_diff.txt
        2 kB
        Kathey Marsden
      2. derby-5427_test_diff.txt
        0.9 kB
        Kathey Marsden

        Issue Links

          Activity

          Myrna van Lunteren made changes -
          Link This issue relates to DERBY-6426 [ DERBY-6426 ]
          Knut Anders Hatlen made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Gavin made changes -
          Workflow jira [ 12634896 ] Default workflow, editable Closed status [ 12802121 ]
          Kathey Marsden made changes -
          Fix Version/s 10.8.3.0 [ 12323456 ]
          Fix Version/s 10.8.2.3 [ 12318540 ]
          Kathey Marsden made changes -
          Link This issue relates to DERBY-5209 [ DERBY-5209 ]
          Kathey Marsden made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 10.8.2.3 [ 12318540 ]
          Fix Version/s 10.9.0.0 [ 12316344 ]
          Resolution Fixed [ 1 ]
          Kathey Marsden made changes -
          Affects Version/s 10.7.1.4 [ 12315902 ]
          Affects Version/s 10.8.2.2 [ 12317968 ]
          Priority Critical [ 2 ] Major [ 3 ]
          Myrna van Lunteren made changes -
          Affects Version/s 10.8.2.2 [ 12317968 ]
          Affects Version/s 10.8.2.1 [ 12317957 ]
          Kathey Marsden made changes -
          Attachment derby-5427_test_diff.txt [ 12498833 ]
          Kathey Marsden made changes -
          Issue & fix info High Value Fix,Repro attached,Workaround attached [ 10422,10424,10427 ] High Value Fix,Patch Available,Repro attached,Workaround attached [ 10422,10102,10424,10427 ]
          Kathey Marsden made changes -
          Attachment derby-5427_diff.txt [ 12498829 ]
          Kathey Marsden made changes -
          Link This issue is related to DERBY-4565 [ DERBY-4565 ]
          Kathey Marsden made changes -
          Assignee Kathey Marsden [ kmarsden ]
          Kathey Marsden made changes -
          Field Original Value New Value
          Description If jdbcapi.AuthenticationTest is run without changing the derby.stream.error.extendedDiagSeverityLevel as is done in the test, it generates thread dumps and javacores for IBM jvms. I beleive the errors in this test are expected user errors and not crashes so they should generate a thread dump or javacore. To reproduce remove this line from test:


             //Derby-4856,set the property to avoid thread dump and diagnostic info
                  sysprops.put("derby.stream.error.extendedDiagSeverityLevel","50000");


          Until fixed, users can work around the issue by setting derby.stream.error.extendedDiagSeverityLevel to 50000 as is done in the test.


          If jdbcapi.AuthenticationTest is run without changing the derby.stream.error.extendedDiagSeverityLevel as is done in the test, it generates thread dumps and javacores for IBM jvms. I beleive the errors in this test are expected user errors and not crashes so they should *not* generate a thread dump or javacore. To reproduce remove this line from test:


             //Derby-4856,set the property to avoid thread dump and diagnostic info
                  sysprops.put("derby.stream.error.extendedDiagSeverityLevel","50000");


          Until fixed, users can work around the issue by setting derby.stream.error.extendedDiagSeverityLevel to 50000 as is done in the test.


          Kathey Marsden created issue -

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development