Bug 692944

Summary: starting aviary fails when axis2 tries to load from /usr/lib on system with wso2-axis2 libraries in /usr/lib64
Product: Red Hat Enterprise MRG Reporter: Matthew Farrellee <matt>
Component: condor-aviaryAssignee: Pete MacKinnon <pmackinn>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: DevelopmentCC: mkudlej
Target Milestone: 2.0   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-04 14:28:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthew Farrellee 2011-04-01 18:47:49 UTC 
$ rpm -q condor-aviary wso2-axis2  
condor-aviary-7.6.0-0.4.el6.x86_64
wso2-axis2-2.1.0-0.4.el6.x86_64

$ CONDOR_CONFIG=only_env _CONDOR_LOG=$PWD _CONDOR_WSFCPP_HOME=/usr /usr/sbin/aviary_query_server -t -f
...
ERROR "Failed to initialize Axis2SoapProvider"

Find the real reason in aviary_query.axis2.log,

[error] class_loader.c(152) Loading shared library /usr//lib/libaxis2_http_sender.so  Failed. DLERROR IS /usr//lib/libaxis2_http_sender.so: cannot open shared object file: No such file or directory

The issue appears to be axis2 looking only in /usr/lib, while the library is present in /usr/lib64,

$ rpm -qf /usr/lib64/libaxis2_http_sender.so.0.6.0 
wso2-axis2-2.1.0-0.4.el6.x86_64

A temporary workaround is to symlink into /usr/lib, which must also be done for libaxis2_http_receiver and libwsf_cpp_msg_recv.
Comment 1 Matthew Farrellee 2011-04-04 14:28:47 UTC 

*** This bug has been marked as a duplicate of bug 693384 ***