qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8220) [linearstore] Error messages: "JournalInactive:<queue name> couldn't setup next firing"
Date Tue, 24 Jul 2018 13:34:00 GMT

    [ https://issues.apache.org/jira/browse/QPID-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554246#comment-16554246

ASF subversion and git services commented on QPID-8220:

Commit 428eafa1f65e22e04ea63b73aebcc192282df72c in qpid-cpp's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=428eafa ]

QPID-8220: Proposed fix for timer error message issue, also minor change to error message
itself to make less confusing

> [linearstore] Error messages: "JournalInactive:<queue name> couldn't setup next
> ---------------------------------------------------------------------------------------
>                 Key: QPID-8220
>                 URL: https://issues.apache.org/jira/browse/QPID-8220
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>            Reporter: Kim van der Riet
>            Assignee: Kim van der Riet
>            Priority: Major
> Under some multi-threaded scenarios, the linearstore inactivity timer causes error messages
to appear in the log file:
> {noformat}
> JournalInactive:<queue name> couldn't setup next firing: -XXXXXXXXXXXns[XXXms]
> {noformat}
>  This is caused by a multi-threaded scenario described in detail [here|https://bugzilla.redhat.com/show_bug.cgi?id=1599778#c12].
This bug appears to be benign other than the possibly large number of error messages that
appear in the broker log files.

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