RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 600925 - Please upgrade CLucene 0.9.21 to 0.9.21b to avoid multithread problems
Summary: Please upgrade CLucene 0.9.21 to 0.9.21b to avoid multithread problems
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: clucene
Version: 6.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jaroslav Reznik
QA Contact: desktop-bugs@redhat.com
URL: http://sourceforge.net/project/showno...
Whiteboard:
Depends On:
Blocks: 600993
TreeView+ depends on / blocked
 
Reported: 2010-06-06 17:51 UTC by Robert Scheck
Modified: 2010-11-10 19:58 UTC (History)
6 users (show)

Fixed In Version: clucene-0.9.21b-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
CLucene has been upgraded to binary compatible version 0.9.21b, fixing multithreading issues (old CLucene wasn't thread safe).
Clone Of:
Environment:
Last Closed: 2010-11-10 19:58:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2010-06-06 17:51:08 UTC
Description of problem:
Please upgrade immediately CLucene 0.9.21 to 0.9.21b to avoid multithread
problems. CLucene 0.9.21b contains a binary compatible fix which fixes a 
potential segfault when used in a multithreaded application. Further details
here: http://sourceforge.net/project/shownotes.php?release_id=635383

CLucene 0.9.21b will be required for Zarafa 6.40.0 hitting the EPEL 6 beta
repository soon. Without CLucene 0.9.21b, the multithreaded zarafa-indexer
is going to crash (reproducible here with 0.9.21).

Version-Release number of selected component (if applicable):
clucene-0.9.21-5.el6

How reproducible:
Everytime

Actual results:
clucene-0.9.21-5.el6

Expected results:
clucene-0.9.21b-1.el6 or better... ;-)

Comment 2 RHEL Program Management 2010-06-07 11:12:54 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 5 Jaroslav Reznik 2010-06-24 11:40:46 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
CLucene has been upgraded to binary compatible version 0.9.21b, fixing multithreading issues (old CLucene wasn't thread safe).

Comment 7 releng-rhel@redhat.com 2010-11-10 19:58:18 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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