Chapter 4. Verified and Resolved Issues

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}.

The LD_LIBRARY_PATH variable was overridden by the apachectl script.

This issue is resolved in JBoss Core Services {JBCSRevision}, and LD_LIBRARY_PATH will no longer be modified when using apachectl.

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.

When using LDAP secure a SSLException: Received fatal alert: insufficient_security error was thrown.

This issue is resolved in JBoss Core Services {JBCSRevision}.

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}.

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}.

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}.

The postinstall script on Solaris references an incorrect path.

This issue is resolved in JBoss Core Services {JBCSRevision}.

The apr* and libapr* 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.

When using ab on powerPC all requests would timeout, and the return code of ab would be 119 instead of the expected 0.

This issue is resolved in JBoss Core Services {JBCSRevision}.

When installing JBCS on RHEL 7 there was a dependency on the optional channel for the apr-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 included apr files.

The mod_security filename for Windows and Solaris systems was incorrectly mod_security2-jws3.so.

This issue is resolved in JBoss Core Services {JBCSRevision}, and is now correctly labeled mod_security2.so.

The jbcs-httpd24-2.4/httpd/sbin/apxs script references EWS_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}.

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.

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.

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}.

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.