Bug 725859 - Qpid store asserts during recovery: "Assertion `rd._eo != std::numeric_limits<std::size_t>::max()' failed."
Summary: Qpid store asserts during recovery: "Assertion `rd._eo != std::numeric_limits...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: qpid-cpp
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Kim van der Riet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-26 18:59 UTC by Kim van der Riet
Modified: 2012-08-06 20:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-06 20:06:12 UTC
Type: ---


Attachments (Terms of Use)

Description Kim van der Riet 2011-07-26 18:59:58 UTC
When using the store module with qpidd, the broker will assert during recovery:

jrnl/jcntl.cpp:866: bool mrg::journal::jcntl::jfile_cycle(u_int16_t&, std::ifstream*, bool&, mrg::journal::rcvdat&, bool): Assertion `rd._eo != std::numeric_limits<std::size_t>::max()' failed.

provided more than one file has been used in the store journal.

Comment 1 Kim van der Riet 2011-07-26 19:13:51 UTC
It appears that gcc/libstdc++ 4.6 (which is the version in F15) behaves slightly differently than 4.5 (whcih is in F14). When the std::ifstream reaches the end of the file, the std::ifstream::failbit and std::ifstream::eofbit are set.

In the earlier version (4.5), it was possible to reset the fail bit then read the current read location using tellg(). However, in 4.6, this is not the case, and tellg() returns -1 even after resetting the fail bit.

The logic around this operation was refactored a little so that the clear operation (which clears all the error bits, including eofbit) was performed immediately before the tellg() operation and the closing of the stream.

Fixed in svn r.4468

Comment 2 Fedora End Of Life 2012-08-06 20:06:12 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2012-08-06 20:06:12 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.