db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (Commented) (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 Sun, 02 Oct 2011 16:36:34 GMT

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

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

Currently, we are using whether a booted database get a session level error to determine whether
to generate a thread dump/javacore. Adding the logic on top of that with whether it is a active
session sounds more accurate to determine a Derby crash situation occur or not. In AuthenticationTest
case, Derby is not crashing. If we add whether it is a active session logic to the code, it
should be closer for the fix of DERBY-4586 with the goal to detecting Derby is crashing. Can
anyone suggest how to determine whether we have a active session or not?
                
> 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.
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

        

Mime
View raw message