db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5427) Unauthorized shutdown should not generate thread dump and javacore. AuthenticationTest dumps over 20 javacores with IBM JVM for normal user errors
Date Fri, 23 Sep 2011 05:13:26 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113158#comment-13113158
] 

Lily Wei commented on DERBY-5427:
---------------------------------

The test generates more than 20 unauthorized shutdown errors. The numbers of javacore files
depend on number of the same unauthorized shutdown error. To fix this from error point of
view, we need to increase the error level for “ERROR 08004: Database connection refused”.
As fix for DERBY-4856, we did not decide to change the error level for ERROR 08004. This is
a good time to revisit this issue. Should we increase the error level for ERROR 08004 to be
higher to avoid the javacore for IBM JVM instead of the workaround fix by setting derby.stream.error.extendedDiagSeverityLevel
to 50000?

> 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
>            Priority: Critical
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message