qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lorenz Quack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-7161) System test output lost owing to orphaned shutdown hooks
Date Tue, 29 Mar 2016 08:28:25 GMT

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

Lorenz Quack resolved QPID-7161.
    Resolution: Fixed

looks good to me

> 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
>            Assignee: Lorenz Quack
>            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

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

View raw message