-
Bug
-
Resolution: Done
-
Critical
-
JWS 3.1.0 GA
-
Release Notes
-
-
-
-
-
-
-
As of the new jbcs-httpd24-httpd-libs sub-package introduced by JBCS-252 there is an issue with the installation process of tomcat-native. The jbcs-httpd24-httpd-libs package filters out the auto-provides/requires of the libapr SOs, so now the auto-requires for APR that's generated by tomcat-native is unsatisfied. This means that even though there is an explicit dependency on jbcs-httpd24-httpd-libs, which provides the required APR libraries, tomcat-native will also install apr/apr-util as a dependency.
We need to filter out the APR libraries from the auto generated requires of tomcat-native.
It is also noteworthy that this isn't a functional issue, tomcat-native still uses the right APR because of the rpath of the SO.
# grep "APR version" /var/log/tomcat8/catalina.2017-02-27.log 27-Feb-2017 14:15:00.974 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library 1.2.8 using APR version 1.5.2. # ldd /usr/lib64/libtcnative-1.so | grep -i apr libapr-1.so.0 => /opt/rh/jbcs-httpd24/root/usr/lib64/libapr-1.so.0 (0x00007f2c47898000)
The biggest problem that I see coming from this is that if the RHEL repository is disabled (and therefore an install can't get access to apr/apr-util) the tomcat-native installation will fail because it can't get the APR libraries that it doesn't even need/use.
- is caused by
-
JBCS-252 httpd fails to start if apr/apr-util is installed prior to installing jbcs-httpd24-httpd
- Closed