[jira] [Updated] (QPID-7161) System test output lost owing to orphaned shutdown hooks

["Keith Wall (JIRA)" <ji...@apache.org>]

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

Keith Wall updated QPID-7161:
-----------------------------
    Priority: Minor  (was: Major)

> System test output lost owing to orphaned shutdown hooks
> --------------------------------------------------------
>
>                 Key: QPID-7161
>                 URL: https://issues.apache.org/jira/browse/QPID-7161
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Tests
>            Reporter: Keith Wall
>            Priority: Minor
>
> When the Broker exits, normally {{AbstractSystemConfig}} organises for the shutdown hook to be removed ({{#onClose}}).  If {{AbstractSystemConfig}} fails to close all its children, the step to remove the shutdown hook never gets executed.  For normal production use cases this is harmless; the Broker is going down anyway.  However when testing the Broker using its system test suite this is problematic.
> Our Logback configuration associates threads to test specific log file.  The ShutdownHook still maintains this association, even though QpidTestCase has already told Logback that the test is through {{org.slf4j.MDC#remove}}.  As Logback believes the test is through, when the Shutdown hook awakes and logs, Logback truncates the tests' logfiles, removing the details of why the test actually failed in the first place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org