Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1100741

Summary:	LevelDB tests fail on RHEL 5
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Jakub Markos <jmarkos>
Component:	Server	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Gencur <mgencur>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	gsheldon, jdg-bugs, mhusnain
Target Milestone:	CR1
Target Release:	6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The native LevelDB JNI library used by the LevelDB store is built using the C++ compiler available in Red Hat Enterprise Linux 6, which makes the resulting binary ABI-incompatible with Red Hat Enterprise Linux 5. As a result, the LevelDB JNI library fails to load with a linker error reporting a missing version symbol (<literal>/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found</literal>). No workaround is available. Users must avoid using the LevelDB cache store on deployments which need to target Red Hat Enterprise Linux 5.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-26 14:03:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1104639

Comment 2 Tristan Tarrant 2014-05-23 16:57:18 UTC

This is the build we are using

https://brewweb.devel.redhat.com/buildinfo?buildID=334667

The problem is that the native implementation is in C++ which means it requires a specific version of the stdlib c++ package which is not ABI compatible. We need to verify if using a RHEL5 build instead will enable running across RHEL 5, 6 and 7

Comment 3 Jakub Markos 2014-07-01 07:55:47 UTC

Fixed in CR1, now fails on https://bugzilla.redhat.com/show_bug.cgi?id=1108089

Comment 4 Martin Gencur 2014-07-04 08:16:51 UTC

This was fixed. We don't need to mention it in release notes unless we want to mention issues that were in Beta release notes and fixed for GA.