-
Language:
English
-
Language:
English
Red Hat Training
A Red Hat training course is available for Red Hat JBoss Core Services
Chapter 4. Verified and Resolved Issues
4.1. Verified JIRAs
The following JIRAs have been verified in this release:
- JBCS-72 - Solaris 11: Apache HTTP Server SSLProxyEngine: [proxy_http:error] End of file found
When using Apache Httpd on Solaris 11 as a reverse proxy with
SSLProxyEngine
enabled, a[proxy_http:error] End of file found:
error is thrown.This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-65 - LD_LIBRARY_PATH entries exported in unix session are overriden in apachectl script
The
LD_LIBRARY_PATH
variable was overridden by theapachectl
script.This issue is resolved in JBoss Core Services {JBCSRevision}, and
LD_LIBRARY_PATH
will no longer be modified when usingapachectl
.
- JBCS-64 - StickySessions don’t work in mod_cluster for ProxyPass from unenabled context
Sticky sessions are not preserved when using
ProxyPass
from an unenabled context to an unenabled one.This issue is resolved in JBoss Core Services {JBCSRevision}, and sticky sessions are now preserved correctly.
- JBCS-62 - Ssl handshake error with LDAP secure
When using LDAP secure a
SSLException: Received fatal alert: insufficient_security
error was thrown.This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-55 - ProxyErrorOverride=On causes workers in error state after 500 errors
When using
ProxyErrorOverride
to host custom error pages on Apache Httpd the worker will be marked as down if the backend replies with a 50x error code.This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-54 - Unable to access deployed application via mod_cluster when balancer name contains capital letters
Previously mod_cluster was unable route requests to backends defined with capital letters, even if contexts were enabled.
This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-53 - mod_jk shmem segfault
There was an issue in mod_jk where
jk_shmem.hdr
would become corrupted, resulting in segfaults.This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-41 - JBCS postinstall pointing to /opt/jws3-0 Solaris
The
postinstall
script on Solaris references an incorrect path.This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-38 - apr*, libapr* modules in rhel7 zips
The
apr*
andlibapr*
modules were previously symlinks, referencing the local modules in RHEL 7 distributions.This issue is resolved in JBoss Core Services {JBCSRevision}, as these modules are now included.
- JBCS-32 - Apache Benchmark is failing on PPC64
When using
ab
on powerPC all requests would timeout, and the return code ofab
would be 119 instead of the expected 0.This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-31 - RPM: dependency on base-os 'apr-util-ldap' package from '-optional' channel
When installing JBCS on RHEL 7 there was a dependency on the
optional
channel for theapr-util-ldap
package.This issue is resolved in JBoss Core Services {JBCSRevision}, as a
mod_ldap
package has been created, and JBoss Core Services utilizes the includedapr
files.
- JBCS-30 - ZIP: mod_security so filename contains jws3 on Windows and Solaris
The
mod_security
filename for Windows and Solaris systems was incorrectlymod_security2-jws3.so
.This issue is resolved in JBoss Core Services {JBCSRevision}, and is now correctly labeled
mod_security2.so
.
- JBCS-25 - RHEL: apxs script contains variable EWS_HOME
The
jbcs-httpd24-2.4/httpd/sbin/apxs
script referencesEWS_HOME
. This environment variable is used by the EWS product, and may refer to a different directory than the JBCS Apache Httpd installation.This issue is resolved in JBoss Core Services {JBCSRevision}.
- JBCS-138 - Solaris: apachectl and httpd won’t start, wrong configuration directory
After installing Apache Httpd on Solaris and running the
postinstall
script, the service will not start due to the hardcoded path not being corrected.This issue is resolved in JBoss Core Services {JBCSRevision}, as the
postinstall
script updates the path correctly.
- JBCS-169 - Distribute an selinux policy in RHEL zips for httpd
The selinux RPM policy was changed; however, the zip distribution used the previous selinux policies.
This issue is resolved in JBoss Core Services {JBCSRevision}, as the zip distribution includes the latest selinux policy.
- JBCS-156 - It appears that the ModSecurity module sometimes fails to increment an integer in persistent storage when many concurrent transactions are sent to the Apache web server
The ModSecurity module would sometimes fail to increment an integer in the persistent storage in case of concurrent transactions.
This issue is resolved in JBoss Core Services {JBCSRevision}.
4.2. Resolved Issues
The following issues have been included in this release, but have yet to be functionally tested:
- JBCS-29 - RPM: JBCS mod_security debuginfo package conflicts with JWS one
When installing JBCS Apache Httpd on a RHEL 6 system that already contains JWS 3 packages the installation would fail, as it attempts to install mod_security from both sources.
This issue is resolved in JBoss Core Services {JBCSRevision}, as each set of packages contains the associated product name.