[
https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114752#comment-13114752
]
Kathey Marsden commented on DERBY-5427:
---------------------------------------
On a simple functional level, the task of DERBY-4586 was to generate a thread
dump/javacore when Derby crashes. This is not a crash so should not generate a
javacore, so users and the tests should not have to work around generating
javacores in this situation by setting
derby.stream.error.extendedDiagSeverityLevel ,
8004 is currently a session level error which seems correct to me.
So I think the problem here is that our determination of whether this situation
is a a crash is a bit off.
As I recall the determination of a crash was when we got a session level error
on a booted database. Perhaps it should be instead if we get a session level
error on an active session.
> 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
