1.2.2. Known Issues

JON Plugin

738826 - [tomcat] Start/Stop/Restart operation should support RPM System V init script with different service names

When configuring JBoss Enterprise Server’s Tomcat server which utilizes System V Init service scripts, the service name cannot be changed.

This is a known issue in JBoss Enterprise Web Server 2.0.1. Currently, no workaround exists for this issue because JBoss Enterprise Server’s JBoss Operations Network (JON) does not allow service name changes.

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 should 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.0.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 is changed by modifying the Tomcat server.xml file, JBoss Operations Network (JON) does not discover the new connector. The old connector is kept in the inventory and it is not valid.

This is a known issue in JBoss Enterprise Web Server 2.0.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.

963264 - RFE - JON Tomcat plugin + Tomcat as Windows service

When JBoss Enterprise Web Server’s Tomcat is installed as a windows service, expected behavior is for it to start and stop as a service (using net start tomcat6 and net stop tomcat6). However, JBoss Operations Network uses the startup.bat and shutdown.bat files, which start Tomcat in a windows console instead of as a service.

This is known issue for JBoss Enterprise Web Server 2.0.1. As a workaround for this issue, create two scripts in the CATALINA_HOME\bin directory and update the startup.bat and shutdown.bat script fields in the JBoss Operations Network interface’s Tomcat configuration tab.

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.0.1 JBoss Operations Network (JON) plugin and there is currently no workaround for this problem.

583996 - EWS Tomcat: "Store Configuration" operation doesn't appear to do anything?

In a running implementation of JBoss Enterprise Web Server’s JBoss Operations Network (JON), selecting the Store Configuration option in the Operations menu does not update the server.xml file. This occurs because the StoreConfig MBean used to persist changes to server.xml was not included in the version of Tomcat that shipped with JBoss Enterprise Web Server.

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

httpd

962819 - Apache Use of LDAP+SSL Doesn't Work on Windows

Httpd partially supports the Windows operating system LDAP SDK. The SSL for secure LDAP should be stored in the registry but this is not supported by httpd/apr. On Windows, a combination of LDAP and SSL does not work properly and an error displays:

LDAP: SSL support unavailable: LDAP: CA certificates cannot be set using this method, as they are stored in the registry instead.

Copy to Clipboard Toggle word wrap

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

978084 - CVE-2013-1862 httpd: mod_rewrite allows terminal escape sequences to be written to the log file [jbews-2]

It was found that enabling mod_rewrite on 64-bit versions of Windows Server 2008 and Windows Server 2008 R2 running Red Hat JBoss Web Server 2.0.1 could cause an httpd thread to crash, and the httpd process to restart.

mod_cluster

958990 - mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1

In JBoss Enterprise Web Server, setting CreateBalancers 1 in /conf.d/mod_cluster.conf without setting the stickysession=JSESSIONID|jsessionid configuration displays the following segmentation fault information:

[notice] child pid 7787 exit signal Segmentation fault (11)

Copy to Clipboard Toggle word wrap

This is a known issue in JBoss Enterprise Web Server 2.0.1. As a workaround, add the stickysession element to the CreateBalancers configuration. For example:

CreateBalancers 1
ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid

Copy to Clipboard Toggle word wrap

960246 - Regression in ProxyPass integration

Due to a regression from an earlier version of mod_proxy_cluster.so included in JBoss Enterprise Web Server, accessing a directory (for example /app/clusterbench/requestinfo/ returns a HTTP 503 error.

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

963723 - mod_cluster: proxy DNS lookup failure with IPv6 on Solaris

Java returns IPv6 with a zone value similar to 2001:db8:0:f101::1%2. Subsequently, when returning a node address, the modcluster subsystem sends the IPv6 information as it exists in Java. In Solaris, apr_sockaddr_info_get() does not support the returned format and fails to resolve the IP as a host name. As a result, httpd mod_cluster does not work as expected IPv6 node addresses.

This is a known issue in JBoss Enterprise Web Server 2.0.1. The workaround for this issue is to use address="hostname" in the web subsystem connector.

mod_jk

901010 - mod_jk doesn't support IPv6

The version of mod_jk included with JBoss Enterprise Web Server 2 does not support IPv6.

This is an upstream bug and a known issue for JBoss Enterprise Web Server 2.0.1. No workaround is currently available for this issue.

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

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.

Copy to Clipboard Toggle word wrap

This is a known issue in JBoss Enterprise Web Server 2.0.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.

900794 - Mod_jk: recover_time is not properly used

The recover_time value is only applied correctly once (the first time). The problem manifests when recover_time is set to a value greater than 60 seconds and is greater than the value of worker.maintain. After the first recovery attempt concludes and the worker errors return to the global error state, the worker is placed in recovery mode again on the next invocation of the worker.maintain method.

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

tomcat6,tomcat7

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

When an IPv6 address is used to start Tomcat 6 or 7 on Windows and them 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

Copy to Clipboard Toggle word wrap

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

979423 - Tomcat files not relabeled after installation of selinux policy

After installing SELinux policy for Tomcat rpms, the Tomcat files are not relabelled in JBoss Enterprise Web Server, resulting in incorrect context based on the newly installed policy.

This is a known issue in JBoss Enterprise Web Server 2.0.1. As a workaround for this issue, relabel the filesystem by using any of the following commands as a user with root privileges:

fixfiles restore /

Copy to Clipboard Toggle word wrap

restorecon -r /

Copy to Clipboard Toggle word wrap

901173 - Tomcat6 and tomcat7 installs the EL API package to alternatives using the same name "el_api"

During the RPM installation for tomcat6 and tomcat7, alternatives are configured for el_api. Both versions of tomcat use the same name (el_api)), due to which the tomcat version installed later overwrites the version installed first. Additionally, both builds use the alternatives el_api and el_api_1_0 instead of the correct version (tomcat6 uses version 2.1 while tomcat7 uses 2.1).

This is a known issue in JBoss Enterprise Web Server 2.0.1. A workaround for this issue is to use update-alternatives to install the desired version of the EL API.

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 the newly created host is not persistently added to the Tomcat configuration. The new host is added after Tomcat is restarted, which is not expected behavior.

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

971866 - Remove libcap-devel requirement from apache-commons-daemon-jsvc-eap6

JBoss Enterprise Web Server’s apache-commons-daemon-jsvc-eap6 file requires the missing libcap-devel package instead of the libcap package, which is available.

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

956509 - add storeconfig to EWS 2.0.1

JBoss Operations Network did not work as expected because the storeconfig components in tomcat 6 and 7 were missing. The missing StoreConfig components are now available in RPM distribution.

RPM users can install the distribution using the executable jar in the /usr/share/tomcat7/lib directory.

This is a known issue in JBoss Enterprise Web Server 2.0.1. As a workaround, ZIP distribution users can open the RPM using the rpm2cio [rpmname] | cpio -idv command. From the output, copy the JAR file to the tomcat lib directory.

StoreConfig uses a LifecycleListener which must be configured as a Listener in server.xml.

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 for several attributes and displays an exception for an invalid character instead. This character is normally used as a group delimiter for the IPv6 addressed.

This is a known issue for JBoss Enterprise Web Server 2.0.1. No workaround currently exists for this issue.

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.0.1 and there is currently no workaround for this problem.

unspecified

956346 - Hibernate4 javadoc must be installed to versioned directory with unversioned symlink

As part of productization, aggregate javadocs are installed into a naming scheme similar to "_javadocdir"/%"name"-%"namedversion", where %"name" is the package name and %"namedversion" is the full productized version (this is not the same as the RPM %"version"). Subsequently, an unversioned symbolic link is added. The hibernate4 javadoc currently uses an unversioned directory, which does not match packages. As a result, wildcards used in the file exacerbate this problem.

This is a known issue for JBoss Enterprise Web Server 2.0.1 and currently no workaround exists to fix this problem.