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 (Updated) (JIRA)" <ji...@apache.org> on 2011/10/12 23:37:11 UTC

[jira] [Updated] (DERBY-5427) Unauthorized shutdown should not generate thread dump and javacore. AuthenticationTest dumps over 20 javacores with IBM JVM for normal user errors

     [ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-5427:
----------------------------------

    Issue & fix info: High Value Fix,Patch Available,Repro attached,Workaround attached  (was: High Value Fix,Repro attached,Workaround attached)

Marking patch available as I would like feedback on the solution. I ran AuthenticationTest but not the full set of regressions yet.
                
> Unauthorized shutdown should not generate thread dump and javacore. AuthenticationTest dumps over 20 javacores with IBM JVM for normal user errors
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5427
>                 URL: https://issues.apache.org/jira/browse/DERBY-5427
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.8.2.1
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Critical
>         Attachments: derby-5427_diff.txt
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira