4. Known Issues

JON Plugin

822250 - Tomcat6 mod_cluster config file

In JBoss Enterprise Web Server, Mod_cluster config file error is displayed on the Inventory Connections screen even after configuring the file. This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

803093 - [Tomcat Plugin] Changing an existing connector type results in new connector type not being discovered

In JBoss Enterprise Web Server, when an existing Tomcat connector was changed by modifying Tomcat’s server.xml file, JBoss Operations Network (JON) did not discover the new connector. The old connector remains in the inventory and is invalid.

This is a known issue in JBoss Enterprise Web Server 2.1. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector.

703562 - Tomcat plugin missing support for JNDI configured Datasources

The JBoss Enterprise Web Server’s Tomcat plugin is used to expose configured JNDI Datasources. The plugin is expected to provide relevant Datasource/Connection Pool information but instead it does not provide any information for JNDI Tomcat Datasources.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

952674 - JON Tomcat user database - union displayed names of tomcat groups, roles and users

JBoss Enterprise Web Server’s JBoss Operations Network (JON) plugin user interface displays the names of groups and users enclosed within quotation marks ("") but the names of roles are not within quotation marks.

This is a known issue in the JBoss Enterprise Web Server 2.1 JBoss Operations Network (JON) plugin and there is currently no workaround for this problem.

1120696 - EWS RPM installed Tomcat version is not discovered

When JBoss Enterprise Web Server is installed using RPMs, the JON Tomcat plugin is not able to discover the Tomcat version number.

This is a known issue in JBoss Enterprise Web Server 2.1 and no workaround is currently available.

httpd

1086412 - SSLFIPS option does not operate the same as RHEL httpd

In JBoss Enterprise Web Server, the SSLFIPS option does not operate as expected.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

968389 - private key before PEM certificate causes Segfault

In JBoss Enterprise Web Server sending a request via a mod_proxy reverse proxy to a https backend results in a segfault. Using gdb shows that having the private key before the certificate in SSLProxyMachineCertificateFile triggers the segfault.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

1118391 - mod_snmp MS Windows known issues

When using JBoss Enterprise Web Server, two unexpected problems occur. Firstly, the mod_snmp agent starts on the UDP:161 default port even if a configuration agentaddress 1610 is specified in snmpd.conf. Secondly, when httpd starts, no notice appears in the httpd error_log file. The expected error message starts with the following:

[notice] SNMP: generic logger: Could not log error-info\n

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

978978 - Unexpected differences in httpd/include/ap_config_layout.h in ZIP and RPM

In JBoss Enterprise Web Server 2.1, the following C macros are available in the ZIP distribution but are not present in the RPM distribution in httpd/include/ap_config_layout.h:

#define DEFAULT_EXP_LIBEXECDIR "/usr/lib/httpd/modules" #define DEFAULT_REL_LIBEXECDIR "/usr/lib/httpd/modules" #define DEFAULT_EXP_INSTALLBUILDDIR "/usr/lib/httpd/build" #define DEFAULT_REL_INSTALLBUILDDIR "/usr/lib/httpd/build"

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

1118395 - mod_snmp Solaris known issues

When using JBoss Enterprise Web Server, an error displayed in the httpd ssl_error_log file during the httpd start up process using a configured mod_snmp:

[Thu Jul 10 09:25:45 2014] [error] SNMP: sconfig is not available

However, the httpd starts and apache httpd snmp MIBs are accessible by snmpwalk.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

1131387 - mod_substitute is missing on Windows

In JBoss Enterprise Web Server, the httpd module mod_substitute is missing in Microsoft Windows build. This is a known issue in JBoss Enterprise Web Server 2.1.

mod_cluster

1025057 - SSLProxyMachineCertificateFile doesn't support PKCS#8 key format

In JBoss Enterprise Web Server, when a PKCS#8 key generated by OpenSSL is used, JBoss Enterprise Web Server displays the following error and then terminates:

incomplete client cert configured for SSL proxy (missing or encrypted private key?)

The PKCS#8 format is not supported by mod_ssl since mod_ssl uses different functions uses when loading the proxy key pair. This is a known issue in JBoss Enterprise Web Server 2.1. As a workaround, convert from PKCS#8 to the raw PEM encoding of the RSA key and use "openssl pkcs8".

mod_jk

900273 - mod_jk is unable to handle space after equal '=' sign in uriworkermap.properties where worker name includes a hyphen '-'

In JBoss Enterprise Web Server, when a worker name includes the - character and a space is added after the = character in the uriworkermaps.properties file, the following error appears in the mod_jk logs:

[25736:139832971024352] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name jk-stauus in uri map post processing. [25736:139832971024352] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name jk-stauus in uri map post processing.

This is a known issue in JBoss Enterprise Web Server 2.1. A workaround for this issue is to remove the space after the = sign. Therefore, /jk-status|/* = jk-status is changed to /jk-status|/* =jk-status.

tomcat6

978370 - Wrong permissions on /usr/share/tomcat6

When using JBoss Enterprise Web Server 2.1 with Red Hat Enterprise Linux 5, the /usr/share/tomcat6 directory does not have the appropriate permissions set. As a result, virtual hosts cannot be created as expected using the host-manager web application because the tomcat user cannot create a directory in /usr/share/tomcat6.

This is a known issue is JBoss Enterprise Web Server 2.1 and no workaround is currently available for this issue.

tomcat6,tomcat7

899180 - CR1: /host-manager application doesn't persist newly created virtual hosts

When a virtual host is created using the /host-manager/html application, it is successfully created but not persistently added to the Tomcat configuration.

This is a known issue in JBoss Enterprise Web Server 2.1. No workaround is available for this problem.

900901 - Tomcat6/7 doesn't allow character ':' in several properties (server.xml)

JBoss Enterprise Web Server’s version of Tomcat 6 and 7 does not allow the semi-colon character (:) in the server.xml file for several attributes and displays an exception for an invalid character instead. This character is normally used as a group delimiter for the IPv6 addresses.

An IP address should not be used as a defaulthost name in the Engine element, nor should an IP address be used as the name in the Host element. These attributes are intended to be alpha-numeric names. These property names are used in MBean names that disallow characters including ":". Users must use a alpha-numeric name and not depend on IP addresses of any type in those properties. This issue will not be fixed in JBoss Enterprise Web Server.

1115849 - Include store-config sources in src zips

In JBoss Enterprise Web Server, the store-config source files are not included in the source zip.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

901081 - Tomcat[6,7]: Start with security manager fails on RHEL with jdk-ibm16,ibm17

When using JBoss Enterprise Web Server with Red Hat Enterprise Linux with either the IBM JDK 1.6 or 1.7, the startup.sh -security command does not start tomcat (6 or 7) but posts exceptions to the logs instead.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

900978 - IPv6 :: address slowing down Tomcat6/7 on MS Windows

In JBoss Enterprise Web Server, when an IPv6 address is used to start Tomcat 6 or 7 on Windows and then the relevant version of Tomcat is shut down, the shutdown process is unexpectedly slow. Additionaly, during the shutdown process, the catalina.log file logs the following warning:

WARNING: Acceptor thread [http-0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-Acceptor-0] failed to unlock. Forcing hard socket shutdown

This is a known issue for JBoss Enterprise Web Server 2.1 and currently no workaround is available.

1120255 - Wrong JAVA_HOME/JRE_HOME auto-detection on RHEL

When using JBoss Enterprise Web Server 2.1 with Red Hat Enterprise Linux, installing Java from RPM results in the JAVA_HOME or JRE_HOME variable unexpectedly not being set. The tomcat start up scripts are able to automatically detect these variables, but when Java is installed from RPMs, which java translated to /usr/bin/java, which is a symbolic link maintained by alternatives. As a result, the JAVA_HOME and JRE_HOME variables are incorrectly set to /usr. JRE_HOME and JAVA_HOME using this incorrect value has not historically resulted in any problems for users (based on bug reports and user support), but a problem manifests when using the daemon.sh script:

 # ./daemon.sh start' Cannot find any VM in Java Home /usr

# grep 'Cannot find any VM in Java Home' ./*
Binary file ./jsvc matches

The jsvc is only used in daemon.sh, therefore this problem does not manifest when tomcat is started using the startup.sh or catalina.sh scripts but does appear when using daemon.sh.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

tomcat7

1099834 - (doc and close/wontfix) manager and host-manager webapps don't work in TC7 when using security manager

When using JBoss Enterprise Web Server 2.1 with the security manager, running a curl -I on the URLs for the /manager and /host-manager web applications returns an expected HTTP 404 Not Found error. This occurs because when a security manager is enabled, XML descriptors for contexts are not deployed by default, since this is less secure. A workaround for this issue is to set deployXML="true" on the host to enable XML descriptors.

This is a known issue is JBoss Enterprise Web Server 2.1.

1100599 - Tomcat7 - catalina.out contains warning and errors (after shutdown)

When using JBoss Enterprise Web Server 2.1 on Microsoft Windows, starting and then stopping Tomcat7 results in warnings and errors being unexpectedly displayed after Tomcat7 has shut down. The web application [/docs] initiates a thread named [SeedGenerator Thread] but does not stop the thread when it shuts down. As a result, the errors and warnings continue to appear after Tomcat7 shuts down.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

1112157 - (document then close/notabug) tomcat7: ClassNotFoundException: org.apache.catalina.ha.ClusterRuleSet

JBoss Enterprise Web Server does not support catalina-ha.jar file. When Tomcat7 is unzipped with default configuration, a ClassNotFoundException: org.apache.catalina.ha.ClusterRuleSet exception is dispalyed in the Tomcat7 catalina.out. This is a known issue in JBoss Enterprise Web Server 2.1 and no workaround exists for this problem.

unspecified

1116863 - [rpm] hibernate extra source jars

In JBoss Enterprise Web Server 2.1, some source files are included in the Hibernate RPM distribution that are not present in the Hibernate ZIP distribution.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.

1117235 - [rpm] c3p0-0.9.1.2.jar different in rpm and in zip

The /usr/share/java/c3p0-0.9.1.2.jar from the c3p0-0.9.1.2 RPM and the lib/optional/c3p0/c3p0-0.9.1.2.jar from the hibernate ZIP file are not the same when checked for binary equivalency using the md5sum value for each file.

This is a known issue in JBoss Enterprise Web Server 2.1 and there is currently no workaround for this problem.