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 (JIRA)" <ji...@apache.org> on 2011/09/22 19:31:26 UTC
[jira] [Created] (DERBY-5427) Unauthorized shutdown should not
generate thread dump and javacore. AuthenticationTest dumps over 20
javacores with IBM JVM for normal user errors
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 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
[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
Posted by "Lily Wei (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127263#comment-13127263 ]
Lily Wei commented on DERBY-5427:
---------------------------------
+1 The change looks good to me.
> 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, derby-5427_test_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
[jira] [Resolved] (DERBY-5427) Unauthorized shutdown should not
generate thread dump and javacore. AuthenticationTest dumps over 20
javacores with IBM JVM for normal user errors
Posted by "Kathey Marsden (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-5427.
-----------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
10.8.2.3
> 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.7.1.4
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Fix For: 10.8.2.3, 10.9.0.0
>
> Attachments: derby-5427_diff.txt, derby-5427_test_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
[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
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5427:
----------------------------------
Priority: Major (was: Critical)
Affects Version/s: (was: 10.8.2.2)
10.7.1.4
This issue affects 10.7 as well, but I am encountering conflicts backporting the fix. I think I won't bother with that now.
If someone using 10.7 needs it they can look at the back port.
> 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.7.1.4
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Fix For: 10.8.2.3, 10.9.0.0
>
> Attachments: derby-5427_diff.txt, derby-5427_test_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
[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
Posted by "Kathey Marsden (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127838#comment-13127838 ]
Kathey Marsden commented on DERBY-5427:
---------------------------------------
Thanks Lily for the review. Regression's passed fine. I'll go ahead and check this into trunk and 10.8.
> 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, derby-5427_test_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
[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
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[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
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Assigned] (DERBY-5427) Unauthorized shutdown should not
generate thread dump and javacore. AuthenticationTest dumps over 20
javacores with IBM JVM for normal user errors
Posted by "Kathey Marsden (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-5427:
-------------------------------------
Assignee: Kathey Marsden
> 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
>
> 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
[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
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[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
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ 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_test_diff.txt
oops, forgot to attach the test diff.
> 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, derby-5427_test_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
[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
Posted by "Lily Wei (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[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
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5427:
----------------------------------
Description:
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.
was:
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 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.
> 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
[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
Posted by "Lily Wei (JIRA)" <ji...@apache.org>.
[ 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