Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1148807 - [linearstore] Restarting broker with empty journal raises confusing warning
[linearstore] Restarting broker with empty journal raises confusing warning
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
3.0
All All
medium Severity medium
: 3.2
: ---
Assigned To: Kim van der Riet
Matej Lesko
:
Depends On:
Blocks: 785156
  Show dependency tree / graph
 
Reported: 2014-10-02 08:25 EDT by Pavel Moravec
Modified: 2015-10-08 09:09 EDT (History)
5 users (show)

See Also:
Fixed In Version: qpid-cpp-0.32-1
Doc Type: Bug Fix
Doc Text:
Provisioning a durable message (backed up by linearstore journal) and restarting the broker without enqueueing a message into it raised a warning message `Journal .. is uninitialized or corrupted`. This message (on this verbosity level) was confusing to users, as it incorrectly suggested a potential problem with the journal. The fix to Linearstore now uses the uninitialized file as the first journal file in the queue.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-08 09:09:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1238183 None None None Never
Red Hat Product Errata RHEA-2015:1879 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.2 Release 2015-10-08 13:07:53 EDT

  None (edit)
Description Pavel Moravec 2014-10-02 08:25:39 EDT 
Description of problem:
Provisioning a durable message (backed up by linearstore journal) and restarting the broker without enqueueing a message into it raises warning message "Journal .. is uninitialized or corrupted".

This message (on this verbosity level) is confusing for a user, as it suggests some problem with the journal while there is none.

Please change the verbosity to info.

Note however that the log message can appear under different use cases (corrupted journal header) where warn level is appropriate.


Version-Release number of selected component (if applicable):
qpid-cpp 0.22-49


How reproducible:
100%


Steps to Reproduce:
1. service qpidd restart
2. qpid-config add queue DurableQueue --durable
3. service qpidd restart


Actual results:
2014-10-01 16:04:19 [Store] warning Linear Store: Journal "DurableQueue": Journal file /var/lib/qpidd/qls/jrnl/DurableQueue/0add3b06-06ee-4f86-8e17-22e0fd1a67e9.jrnl is uninitialized or corrupted


Expected results:
The log is on info level.


Additional info:
Comment 1 Kim van der Riet 2015-01-06 10:51:32 EST 
This issue has been fixed with checkin r.1649081, the final checkin for a related bug 1160367.

With this checkin, the uninitialized file is now correctly used by the store as the first journal file in the queue.
Comment 4 errata-xmlrpc 2015-10-08 09:09:16 EDT 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-1879.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.