Chapter 5. Known Issues

When attempting to bind on link-local with an IPv6 address the following error is seen:

(22)Invalid argument: AH00072: make_sock: could not bind to address [ffff::ffff:fff:ffff:ffff]:80
no listening sockets available, shutting down
AH00015: Unable to open logs

(22)Invalid argument: AH00072: make_sock: could not bind to address [ffff::ffff:fff:ffff:ffff]:80
no listening sockets available, shutting down
AH00015: Unable to open logs

This is a known issue in JBoss Core Services {JBCSRevision}, and a workaround exists to bind the address in the configuration filewithout using the brackets. For instance, the following configuration snippet would bind correctly:

Listen ffff::ffff:ffff:ffff:ffff%3:80

Listen ffff::ffff:ffff:ffff:ffff%3:80

There is no JSON support for mod_security, and any requests made with a Content-Type of application/json that includes JSON data fails.

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists.

When installing JBCS via the zip distribution, additional files are found in the installation directory.

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists to prevent these files from being included.

On RHEL 6 x86_64 and i386 the RPM package jbcs-httpd24-runtime installs several empty directories. The RHEL 7 version of this package does not install these directories.

This is a known issue in JBoss Core Services {JBCSRevision}.

When SSLOCSPEnable is defined outside of VirtualHost blocks the configuration is not inherited.

This is a known issue in JBoss Core Services {JBCSRevision}, and to workaround the issue place the SSLOCSPEnable directive inside the VirtualHost configuration block.

The default path to the OpenSSL configuration files is incorrect. Any attempts to execute openssl on RHEL or Solaris results in the following error being thrown:

WARNING: can't open config file: /opt/rh/jbcs-httpd24/root/etc/pki/tls/openssl.cnf

WARNING: can't open config file: /opt/rh/jbcs-httpd24/root/etc/pki/tls/openssl.cnf

This is a known issue in JBoss Core Services {JBCSRevision}. To workaround this issue manually define the OPENSSL_CONF environment variable to point to the configuration file location.

When CheckCaseOnly On is enabled and a file is requested that is not present, even with a different case, a HTTP 404 error should be thrown. Instead, a HTTP 300 error is thrown, and files with a common base name are displayed.

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists at this time.

The log format for mod_rt does not correspond with the LogFormat defined in the httpd configuration.

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists at this time.

When jbcs-httpd24-mod_cluster-native or jbcs-httpd24-mod_bmx are uninstalled there will be SELinux info messages included in the removal messages. For instance:

libsemanage.semanage_direct_remove_key: Removing last mod_cluster module (no other mod_cluster module exists at another priority).
libsemanage.semanage_direct_remove_key: Removing last mod_bmx module (no other mod_bmx module exists at another priority).

libsemanage.semanage_direct_remove_key: Removing last mod_cluster module (no other mod_cluster module exists at another priority).
libsemanage.semanage_direct_remove_key: Removing last mod_bmx module (no other mod_bmx module exists at another priority).

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists at this time; however, these messages may be safely ignored.

When installing jbcs-httpd24-httpd on a system that already has apr or apr-util installed httpd will be unable to start, and instead throw the following error:

Starting httpd: /opt/rh/jbcs-httpd24/root/usr/sbin/httpd: symbol lookup error: /opt/rh/jbcs-httpd24/root/usr/sbin/httpd: undefined symbol: apr_crypto_init
                                                           [FAILED]

Starting httpd: /opt/rh/jbcs-httpd24/root/usr/sbin/httpd: symbol lookup error: /opt/rh/jbcs-httpd24/root/usr/sbin/httpd: undefined symbol: apr_crypto_init
                                                           [FAILED]

This is a known issue in JBoss Core Services {JBCSRevision}. To workaround this issue install jbcs-httpd24-httpd-devel, as it contains the necessary linked libraries.

The OPENSSL_ENGINES environment variable is not updated for the zip distrubtions, resulting in httpd failing to start when a non-default SSLCryptoDevice is specified. The following error is seen in Apache httpd’s error log:

SSLCryptoDevice: Invalid argument; must be one of: 'builtin' (none), 'rdrand' (Intel RDRAND engine), 'dynamic' (Dynamic engine loading support)

SSLCryptoDevice: Invalid argument; must be one of: 'builtin' (none), 'rdrand' (Intel RDRAND engine), 'dynamic' (Dynamic engine loading support)

This is a known issue in JBoss Core Services {JBCSRevision}. To workaround this issue set OPENSSL_ENGINES to the included engines directory manually:

OPENSSL_ENGINES=$JBCS_HOME/httpd/lib/engines

OPENSSL_ENGINES=$JBCS_HOME/httpd/lib/engines

The DeflateAlterETag directive is not present by default, resulting in 304 Not Modified responses when using mod_deflate.

This is a known issue in JBoss Core Services {JBCSRevision}. To workaround this issue the ETag header must be removed. This header may be removed by including the Header unset ETag line in the relevant configuration.

When installing jbcs-httpd24 after jboss-eap6 the jbcs-httpd24-openssl package is not updated, resulting in an inability to start httpd.

This is a known issue in JBoss Core Services {JBCSRevision}. To workaround this issue manually update the package by using the following command:

yum update jbcs-httpd24-openssl

yum update jbcs-httpd24-openssl

When attempting to execute service jbcs-httpd24-httpd configtest or service jbcs-httpd24-httpd graceful the following error is thrown:

/usr/libexec/initscripts/legacy-actions/jbcs-httpd24-httpd/graceful: line 2: /sbin/apachectl: No such file or directory

/usr/libexec/initscripts/legacy-actions/jbcs-httpd24-httpd/graceful: line 2: /sbin/apachectl: No such file or directory

This is a known issue in JBoss Core Services {JBCSRevision}. To workaround this issue perform the following steps:

The SSLOCSPResponderCertificateFile is not included in the distribution.

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists at this time.

Using JON with JBoss Web Server, if you add a new Listen port to an Apache HTTP Server may result in the Apache HTTP Server not able to restart. This is because the Listen directive is added at the end of httpd.conf even though it may already be defined in conf.d/ssl.conf. This issue will be fixed in a future release.

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists at this time.

By default, the maximum length of ProxyPass worker name is 96. If the worker name exceeds this limit, an error is displayed.

This is a known issue in JBoss Core Services {JBCSRevision}, and no workaround exists at this time.

The apxs binary is missing in the Sun and Windows builds.

This is a known issue in JBoss Core Services {JBCSRevision}, and the devel packages and debug symbols are provided on-demand.