db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Updated) (JIRA)" <j...@apache.org>
Subject [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
Date Wed, 12 Oct 2011 21:37:11 GMT

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

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

    Attachment: derby-5427_diff.txt

Attached is a patch which fixes this issue, but I don't know if it is the best solution. 
  The critieria for a crash needs to be that we do the thread dump if we get a session level
error while the session is active.  To test whether the session was active we would just check
 database.isActive().  In the problematic authentication cases, database.isActive() was true
and we are actually in a transaction at the time,  but because the user had not successfully
logged in, it should not have been considered an active session.

The attached change actually checks the SQLState for login errors and does not consider that
case an active session. I  wonder if there is not a better and more efficient way to check.

                
> 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

        

Mime
View raw message