5. Resolved Issues

JON Plugin

690957 - EWS Tomcat installed from RPM shutdown fails.

Previously in JBoss Enterprise Web Server, when installing Tomcat using RPMs and managing it via JBoss Operation Network, Tomcat could not be shut down. This was because the JBoss Operation Network Tomcat plugin did not work as expected with the RPM-based Tomcat installation.

The JBoss Operation Network Tomcat plugin is fixed in JBoss Enterprise Web Server 2.1.

786082 - tomcat as a service is not properly detected

Previously in JBoss Enterprise Web Server, the JON Tomcat plugin was not able to discover Tomcat installed as a Microsoft Windows service. In JBoss Enterprise Web Server 2.1, the JON Tomcat plugin is now fixed so that Tomcat is discovered as expected.

1069880 - Discovery of Tomcat fails when started using daemon.sh or jsvc

Previously, when starting Tomcat as a service using the provided daemon.sh script, the JBoss Enterprise Web Server management plugin was unexpectedly unable to discover Tomcat. This problem also occurred when the user created their own jsvc launcher to launch the Tomcat process.

This is now fixed in JBoss Enterprise Web Server 2.1 and Tomcat is discovered as expected when started.

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

When JBoss Enterprise Web Server’s Tomcat is installed as a windows service, it should start and stop as a service using the net start tomcat6 and net stop tomcat6 commands. 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 issue is fixed in JBoss Enterprise Web Server 2.1. Tomcat installed as a Windows service can now be started and stopped as expected using the JBoss Operation Network user interface.

1104581 - Tomcat configured to use SSL is discovered as Tomcat(null) in JBoss ON

Previously when using JBoss Enterprise Web Server with JBoss Operations Network, when Tomcat was configured to use SSL, it was incorrectly discovered as Tomcat(null) instead of correctly identified as Tomcat($PORT).

This problem is now fixed in JBoss Enterprise Web Server 2.1 and Tomcat is correctly discovered as Tomcat($PORT) as expected.

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

Previously, when configuring JBoss Enterprise Server’s Tomcat server which utilizes System V Init service scripts, the service name could not be changed. This was because JBoss Enterprise Server’s JBoss Operations Network (JON) did not allow service name changes.

This is now fixed in JBoss Enterprise Web Server 2.1 and the JBoss Operations Network interface now includes a Service Name field for users to manually specify the desired name for a service.

1119652 - Webappp configuration - Config File field is mandatory

Previously, when using JBoss Enterprise Web Server with JBoss Operations Network, deploying the web application without the context.xml file, the Config File field in the JBoss Operations Network user interface’s web application configuration remained empty. This field was mandatory.

This problem is now fixed in JBoss Enterprise Web Server 2.1 and the Config File field in the JBoss Operations Network user interface is removed.

JON Plugin,tomcat6,tomcat7

956509 - add storeconfig to EWS 2.0.1

Previously, JBoss Operations Network did not work as expected with JBoss Enterprise Web Server because the storeconfig components in tomcat 6 and 7 were missing. The missing StoreConfig components are now available in and this is a resolved issue in JBoss Enterprise Web Server 2.1.

httpd

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

Previously in JBoss Enterprise Web Server, httpd partially supported the Microsoft Windows version of the LDAP SDK. The SSL information 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 did not work correctly and displayed the following error message:

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

This issue is fixed in JBoss Enterprise Web Server 2.1 and the secure LDAP information is now stored in the registry without errors as expected.

1115407 - Case insensitive URI comparison when using SNI

Previously in JBoss Enterprise Web Server, a URI comparison between hostname via SNI and hostname via HTTP displayed the following error for case-sensitivity:

[error] Hostname ABC.xyz.com via SNI and hostname abc.xyz.com via HTTP are different

The URI comparisons must be case-insensitive. This issue is fixed in JBoss Enterprise Web Server 2.1.

1108181 - [rpm][rhel7] Add Requires: apr-util-ldap to httpd22.spec

Previously, JBoss Enterprise Web Server did not automatically install apr-util-ldap (which is a requirement for LDAP authentication on Red Hat Enterprise Linux 7).

In JBoss Enterprise Web Server 2.1, apr-util-ldap was evaluated and removed from the httpd22 file as it is an optional component and available through the optional Red Hat Network channel.

1130169 - Upgrade httpd to version 2.2.26 from 2.2.22

The httpd version in JBoss Enterprise Web Server 2.1 is updated from 2.2.22 to 2.2.26.

1079300 - mod_snmp is not configured in MS Windows and Solaris build by default

Previously in JBoss Enterprise Web Server, the mod_snmp.conf, mod_cluster.conf, and mod_rt.conf files were included in conf.d for the Red Hat Enterprise Linux build but were not included in the Microsoft Windows and Oracle Solaris builds.

These missing files are added into the Microsoft Windows and Oracle Solaris builds in JBoss Enterprise Web Server 2.1. Additionally, mod_snmp and mod_rt are provided with sample configurations and not started by default.

976451 - Bug in ssl_util_ocsp.c breaks http://ocsp.disa.mil

Previously in JBoss Enterprise Web Server, the code in the ssl_util_ocsp.c file was broken. As a result, when the apr_bucket_read parameter returned 0 bytes, it did not indicate the end of the file (EOF). Due to this problem, the code exits prematurely with a false EOF error for some OCSP responders.

This is fixed in JBoss Enterprise Web Server 2.1 so that the code in the ssl_util_ocsp.c file contains the EOF information and operates as expected.

1106516 - mod_snmp.conf configuration in .postinstall makes postinstall non-reentrant

Previously in JBoss Enterprise Web Server, running the .postinstall file more than once resulted in the currentDir prepending process entering into an infinite loop and the process never concluding.

This is fixed in JBoss Enterprise Web Server 2.1 so that running .postinstall more than once works as expected.

984116 - "ProxyErrorOverride On" does not work in mod_proxy_ajp

In JBoss Enterprise Web Server, ProxyErrorOverride On does not work when used with the mod_proxy_ajp module. When accessing a 404 URL in the /app context, a 404 page is displayed from the back end servers such as Tomcat, JBoss Enterprise Application Platform, etc.

This is fixed in JBoss Enterprise Web Server 2.1 and works as expected.

1022520 - WebDAV - httpd.conf typo

Previously in JBoss Enterprise Web Server, the location of the WebDAV lock database was incorrect in the httpd.conf file used for the mod_dav_fs configuration on Solaris and Microsoft Windows.

In JBoss Enterprise Web Server 2.1, the incorrect DAVLockDB var/run/lockdb part of the configuration is now corrected to DAVLockDB run/lockdb and now works as expected.

mod_cluster

1080047 - EWS-2.0 mod_cluster on windows

Previously in JBoss Enterprise Web Server, mod_cluster locks were created and used even when they were not needed due to which a deadlock occurred on an unnecessary session lock.

This is fixed in JBoss Enterprise Server 2.1 where locks are now created and used when necessary. When Maxsessionid is set to 0 (the default and preferred setting), the locks are not created and used, thus avoiding the deadlock.

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

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

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

This issue is fixed in JBoss Enterprise Web Server 2.1.

1107551 - Upgrade mod_cluster to 1.2.9.Final from 1.2.8.Final-redhat-1

The mod_cluster version in JBoss Enterprise Web Server 2.1 is updated from 1.2.8 to 1.2.9.

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

Previously in JBoss Enterprise Web Server, Java returned IPv6 with a zone value similar to 2001:db8:0:f101::1%2. Subsequently, when returning a node address, the modcluster subsystem sent the IPv6 information as it existed in Java. In Solaris, apr_sockaddr_info_get() did not support the returned format and failed to resolve the IP as a host name. As a result, httpd mod_cluster did not work as expected IPv6 node addresses.

This issue is fixed in JBoss Enterprise Web Server 2.1.

1049276 - mod_cluster-manager may break up aliases from a single VirtualHost, causing a messy page

Previously in JBoss Enterprise Web Server, when displaying the individual virtual hosts for a node, mod_cluster-manager displayed a page filled with aliases from a single virtual host interspersed with multiple other instances of the virtual host and its contexts. The result is unclear and can cause confusion for users. This problem occurs with concurrent start ups when JBoss has multiple applications bound to virtual servers that are deployed and enabled at the same time.

This is fixed in JBoss Enterprise Web Server 2.1 and virtual hosts are always displayed correctly (and only once) on the manager page with all the relevant aliases included in the single entry.

This is fixed in JBoss Enterprise Web Server 2.1 and virtual hosts are always displayed correctly (and only once) on the manager page with all the relevant aliases included in the single entry.

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/) returned a HTTP 503 error.

This issue is fixed in JBoss Enterprise Web Server 2.1.

mod_jk

1100602 - mod_jk 1.2.40 IPv6 support does not work on Windows

Previously, mod_jk 1.2.40 IPv6 support did not work on Microsoft Windows as APR resolves addresses on Microsoft Windows differently.

This issue is fixed in JBoss Enterprise Server 2.1. The mod_jk 1.2.40 IPv6 support now works with Microsoft Windows.

1089204 - Upgrade mod_jk to version 1.2.40 from 1.2.36

Previously in JBoss Enterprise Web Server, an outdated version of mod_jk was included in the product, which did not include IPV6 support and various other fixes.

This is now fixed in JBoss Enterprise Web Server 2.1 by including mod_jk version 1.2.40 is included which incorporates the required IPV6 and other miscellaneous bug fixes into the product.

tomcat-native

1089206 - Upgrade tomcat-native to 1.1.30 from 1.1.27

Previously in JBoss Enterprise Web Server, an outdated version of tomcat-native was included in the product, which did not include bug fixes for FIPS issues and does not include support for ECDGE ciphers.

This is now fixed in JBoss Enterprise Web Server 2.1 by including tomcat-native version 1.1.30 is included which incorporates the required FIPS fixes for Red Hat Enterprise Linux 6 and also adds support for ECDHE ciphers to allow Internet Explorer browsers to operate as expected.

tomcat6

1121867 - Getting RPM Tomcat version is not working

Previously, when JBoss Enterprise Web Server was installed using RPM, the /etc/init.d/tomcat{version} version script did not work as expected for Tomcat 6 and 7.

This issue is fixed in JBoss Enterprise Web Server 2.1 and the script option version now works as expected for both versions of Tomcat.

1126423 - [tomcat6] duplicate jars in tomcat6/bin

Previously in JBoss Enterprise Web Server, duplicated JAR files were unexpected available in the Red Hat Enterprise Linux 6 ZIP files for Tomcat.

This issue is fixed in JBoss Enterprise Web Server 2.1 and the duplicated files are now removed.

1071309 - update tomcat6 to 6.0.41

Previously, JBoss Enterprise Web Server included an outdated version of Tomcat 6.x.

This is fixed in JBoss Enterprise Web Server 2.1 and Tomcat 6.0.41 is included in the product as expected.

tomcat6,tomcat7

979423 - Tomcat files not relabelled after installation of selinux policy

In JBoss Enterprise Web Server, the SELinux configuration files and compiled .pp file are available at $confdir/selinux/packages/tomcat7. The compiled .pp file is provided but not installed. As a result, various things fail when installing the module and error messages are not descriptive.

This issue is fixed in JBoss Enterprise Web Server 2.1. The SELinux configuration files are provided and the system administrator must compile and use the policies. For more information, refer the JBoss Enterprise Web Server Installation guide.

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

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

This issue was fixed in JBoss Enterprise Web Server 2.1. The libcap-devel package is now available for the apache-commons-daemon-jsvc-eap6 file as expected.

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

Previously in JBoss Enterprise Web Server, 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 issue is fixed in JBoss Enterprise Web Server 2.1.

tomcat7

1099781 - Tomcat7 daemon.sh did not start

Previously in JBoss Enterprise Web Server the Tomcat7 daemon.sh file did not start as expected on Oracle Solaris. When /opt/jboss-ews-2.1/share/tomcat7/bin/daemon.sh is run under the tomcat user on Solaris, the following error is displayed:

/opt/jboss-ews-2.1/share/tomcat7/bin/daemon.sh: test: argument expected

This issue is fixed in JBoss Enterprise Web Server 2.1.

982787 - broken comment syntax in catalina.sh for tomcat 7

Previously in JBoss Enterprise Web Server, starting Tomcat 7 using the catalina.sh file resulted in a command not found error due to the broken comment syntax in catalina.sh.

This is now fixed in JBoss Enterprise Server 2.1. Starting Tomcat with catalina.sh works as expected.

976411 - tomcat7 rpm verify problem

In JBoss Enterprise Web Server, the output of the following command shows that the file is owned by two packages, tomcat7-el-1.0-api-7.0.40-5_patch_01.ep6.el5 and tomcat7-lib-7.0.40-5_patch_01.ep6.el5:

rpm -qf /usr/share/java/tomcat7/tomcat7-el-1.0-api-7.0.40.jar

As a consequence the following command shows wrong ownership of /usr/share/java/tomcat7/tomcat7-el-1.0-api-7.0.40.jar:

rpm -V tomcat7-el-1.0-api

This issue is fixed in JBoss Enterprise Web Server 2.1.

1054379 - Update tomcat7 from 7.0.40 to 7.0.54

The tomcat version in JBoss Enterprise Web Server 2.1 is updated from 7.0.40 to 7.0.54.

1088261 - WARs outside of the host's appBase are not unpacked, regardless of the value of the Host's unpackWARs setting

Previously in JBoss Enterprise Web Server, when a web application was deployed outside the host’s appBase then it is not unpacked, regardless of the value of the Host’s unpackWARs setting. This was because tomcat’s deployer was not refactored.

This issue is fixed in JBoss Enterprise Web Server 2.1. The web application is deployed and the WAR file is unpacked inside the specified appBase.

unspecified

1115525 - jsvc in different directories

Previously in JBoss Enterprise Web Server, when using the Red Hat Enterprise Linux version, the jsvc binary was missing from the tomcat6/bin directory. For the Oracle Solaris version, jsvc was not available in the share/extras directory. As a result, when the JSVC environment variable was not set, the daemon.sh script in the tomcat{6,7}/bin directory sets the value of JSVC to $CATALINA_BASE/bin/jsvc, which is incorrect.

This is fixed in JBoss Enterprise Web Server 2.1 and the jsvc binary file is available as expected in the tomcat6/bin directory for Red Hat Enterprise Linux and in the share/extras directory for Oracle Solaris.

1113435 - Upgrade Hibernate to 4.2.14.SP1 (from 4.2.13.Final-redhat-1)

Previously, JBoss Enterprise Web Server included an oudated version of Hibernate.

This is fixed in JBoss Enterprise Web Server 2.1, which includes Hibernate version 4.2.14.Final which includes some regression fixes.

1117350 - [rpm] remove javadoc from c3p0-0.9.1.2-3.ep6.el6

Previously in JBoss Enterprise Web Server, the c3p0-0.9.1.2-8_redhat_1.ep6.el5, c3p0-0.9.1.2-8_redhat_1.ep6.el6, and c3p0-0.9.1.2-8_redhat_1.ep6.el7 builds contained a javadoc (located at /usr/share/javadoc/{build_name}/) but was not present in the Red Hat Enterprise Linux 5 RPM or ZIP distribution builds.

This is fixed in JBoss Enterprise Web Server 2.1 and the javadocs are not included in the c3p0-0.9.1.2-8_redhat_1.ep6.el5, c3p0-0.9.1.2-8_redhat_1.ep6.el6, and c3p0-0.9.1.2-8_redhat_1.ep6.el7 builds as expected.