Bug 460706 - Running 32 bit (i386) broker on 64 bit system (x86_64) will fail to correctly find and load modules
Running 32 bit (i386) broker on 64 bit system (x86_64) will fail to correctly...
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: messaging-bugs
Kim van der Riet
Depends On:
  Show dependency treegraph
Reported: 2008-08-29 18:25 EDT by Andrew Stitcher
Modified: 2012-12-07 12:45 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Stitcher 2008-08-29 18:25:20 EDT
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1

[From code inspection]
The default module load location id calculated dynamically based in the platform the broker is running on NOT the type of executable that is running.

This means that a i386 broker running on an x86_64 installation which is perfectly valid (and should be correctly supported) will try to load modules from /usr/lib64/qpidd which will either not contain any modules (if the 64 bit qpidd isn't installed) or will find modules that cannot be loaded (due to wrong architecture) if it is.

The probably fix is to calculate the default module directory at build time (which knows the architecture its building) and not try to calculate at run time.

Reproducible: Always

Steps to Reproduce:
Not observed - bug found from code inspection:

But installing an i386 qpidc/rhm on an x86_64 box should exhibit this bug.
Actual Results:  
I expect that running an i386 qpidd with an bdbstore module will fail to work with the default module directory on an x86_64 machine
Comment 1 Andrew Stitcher 2009-02-05 11:29:39 EST
This has been fixed as of qpidd r694113

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