Details
-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.2.0
-
None
-
RHEL 5, RHEL 6
-
Release Notes
-
Workaround Exists
-
-
It was found that previous versions of the JBoss EAP GUI installer failed to create the necessary symlinks to APR libraries. This issue has been resolved in this release of the product.
-
Documented as Resolved Issue
-
NEW
Description
EAP 5 GUI installer fails to create symbolic links for APR libraries in native component.
How reproducible:
Everytime when installing EAP 5 Native component via GUI Installer.
Expected results:
The following symbolic links are created after installing EAP 5 Native component via GUI Installer.
For RHEL 6:
jboss-ep-5.2/native/lib64/libapr-1.so.0.3.9 -> /usr/lib64/libapr-1.so.0.3.9
jboss-ep-5.2/native/lib64/libapr-1.so.0 -> /usr/lib64/libapr-1.so.0
jboss-ep-5.2/native/lib64/libaprutil-1.so.0.3.9 -> /usr/lib64/libaprutil-1.so.0.3.9
jboss-ep-5.2/native/lib64/libaprutil-1.so.0 -> /usr/lib64/libaprutil-1.so.0
For RHEL 5:
jboss-ep-5.2/native/lib64/libaprutil-1.so.0 -> /usr/lib64/libaprutil-1.so.0
jboss-ep-5.2/native/lib64/libapr-1.so.0 -> /usr/lib64/libapr-1.so.0
jboss-ep-5.2/native/lib64/libaprutil-1.so.0.2.7 -> /usr/lib64/libaprutil-1.so.0.2.7
jboss-ep-5.2/native/lib64/libapr-1.so.0.2.7 -> /usr/lib64/libapr-1.so.0.2.7
Actual results:
Any symbolic links for APR libraries are not created but ASCII text files are created.
