Red Hat JBoss Web Server 2 2.0.1 Release Notes Release Notes for Red Hat JBoss Web Server 2.0.1 Edition 2 Last Updated: 2017-10-19 Red Hat JBoss Web Server 2 2.0.1 Release Notes Release Notes for Red Hat JBoss Web Server 2.0.1 Edition 2 Mandar Joshi Red Hat Engineering Content Services [email protected] Misha Husnain Ali Red Hat Engineering Content Services [email protected] Legal Notice Copyright © 2011 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract These release notes contain important information related to Red Hat JBoss Web Server 2.0.1. Read these Release Notes in their entirety before installing Red Hat JBoss Web Server 2.0.1. Table of Contents Table of Contents .C .H . A. P. .T .E .R . .1 .. .A . B. O. .U . T. .J .B .O . S. .S . E. N. .T .E . R. P. .R .I S. .E . W. E. B. S. E. R. .V .E . R. .3 . 1.1. OVERVIEW 3 1.2. CHANGES IN THIS RELEASE 3 1.2.1. Bug Fixes 3 1.2.2. Known Issues 8 .A .P . P. E. N. .D . I.X . A. .R .E . V. I.S .I O. .N . .H .I S. .T .O . R. Y. .1 .4 . 1 2.0.1 Release Notes 2 CHAPTER 1. ABOUT JBOSS ENTERPRISE WEB SERVER CHAPTER 1. ABOUT JBOSS ENTERPRISE WEB SERVER 1.1. OVERVIEW JBoss Enterprise Web Server is a fully-integrated and certified set of components for hosting Java web applications. It is comprised of the industry's leading web server (Apache HTTP Server), the popular Apache Tomcat Servlet container as well as load balancers (mod_jk and mod_cluster), Hibernate, the Tomcat Native library and others. Supported Configurations For a comprehensive list of supported configurations for JBoss Enterprise Web Server 2.0 and 2.0.1, refer to the JBoss Enterprise Web Server Supported Configurations page. 1.2. CHANGES IN THIS RELEASE 1.2.1. Bug Fixes JON Plugin 865460 - Cannot add a Group to tomcat's UserDatabase Due to missing parameters a public class, adding a group to Tomcat’s UserDatabase using the JBoss Operations Network (JON) interface displays an error: DEBUG [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Throwable was found in creation report for request [10083]. java.lang.IllegalStateException: Name [roles] specified for parameter of operation [createGroup] on MBean [Users:type=UserDatabase,database=UserDatabase] is invalid. The MBean operation does not take a parameter by that name.. A fix is applied to add the missing parameters. As a result, adding a group to Tomcat’s UserDatabase works as expected in JBoss Enterprise Web Server 2.0.1. 865459 - Cannot add a User to tomcat's UserDatabase Due to missing parameters in the public class, adding a user to Tomcat’s UserDatabase using the JBoss Operations Network (JON) interface in JBoss Enterprise Web Server displays an error in agent’s log indicating that the MBean parameters are invalid. A fix is applied to add the missing parameters. As a result, adding users to Tomcat’s UserDatabase using JBoss Operations Network (JON) works as expected in JBoss Operations Network (JON). 688358 - [JBPAPP-6104] JON 2.4.1: User Database "Save" operation fails, but reports Success The add, modify and remove operations in tomcat 6 and 7 do not manipulate the user database as expected. As a result, the JBoss Operations Network interface fails. The plugin logic is now fixed. To ensure JBoss Operations Network works as expected, set readonly="false" in the UserDatabase resource in the server.xml file. 3 2.0.1 Release Notes 921194 - [tomcat] Connectors are not properly discovered and therefore are unavailable along with all their content Due to an issue in the JBoss Enterprise Web Server plug in, the connectors ?-8080 and ?-8009 are down. As a result, Tomcat 7 can not be monitored or managed. The bug in the JBoss Enterprise Web Server plug in is now fixed. As a result, the connectors are now discoverable and are named http- bio-8080 and ajp-bio-8009 as expected and Tomcat 7 can be managed and monitored successfully. 921261 - WebModule is reported as DOWN or UNAVAILABLE due to plug-in expecting stateName to return 1 instead of STARTED The missing MBean for the //localhost/my-simple-webapp WAR file causes all the web applications deployed on Tomcat 7 to be unavailable. The Tomcat 7 support patch contains the updated MBean names. The relevant MBean names are now correct and discoverable as expected. httpd 947579 - httpd 2.2.22 init script does not properly make use of the pid file OpenShift Enterprise contains a cartridge that requires a JBoss Enterprise Application Platform subscription. The JBoss Enterprise Application Platform channel provides an Apache init script that is incompatible with the httpd 2.2.22 init script in the OpenShift Enterprise cartridge. The JBoss httpd service script does not pass the "-p pidfile" flag to killproc resulting in killing openshift-console and openshift-broker services along with all the end user applications that use httpd. The bug in the init script is now fixed. The patch in the httpd 2.2.22 init script now kills the process using its process ID as expected. 973189 - EWS httpd keeps writing logs to old log file after rotated by logrotate JBoss Enterprise Web Server httpd does not write logs to new log file after after it is rotated by logrotate. Expected behavior is to write logs to new log file after rotated by logrotate. This occurs because the httpd.pid file path is incorrect in /etc/logrotate.d/httpd script. This issue is fixed in JBoss Enterprise Web Server 2.0.1. The httpd.pid file path is now corrected in /etc/logrotate.d/httpd script. JBoss Enterprise Server httpd now writes logs to new log file after rotated by log rotate. 900827 - Apache httpd returns 500 status code instead of custom status code when using mod_proxy An issue with Apache http produces wrong status code when using mod_proxy http as a loadbalancer/proxy and a JSP with a custom status code. Instead of custom status code, 500 status code is returned. The bug in the Apache http has now been fixed. Using mod_proxy http as a loadbalancer/proxy and a JSP with a custom status code now returns the custom status code. 901126 - Update postinstall script to check for check for conf file before editing JBoss Enterprise Web Server 2.0 contained mod_snmp and mod_cluster. However, JBoss Enterprise Application Platform does not require these dependencies and therefore the commands that manipulate mod_snmp and mod_cluster in the .postinstall file are not suitable for JBoss Enterprise Application Platform. As a result, the .postinstall file included with JBoss Enterprise 4 CHAPTER 1. ABOUT JBOSS ENTERPRISE WEB SERVER Application Platform 2.0 did not work as expected. This is fixed so that the .postinstall file now includes condition tests in mod_cluster and mod_snmp. As a result, the .postinstall file shipped with JBoss Enterprise Application Platform works as expected. 971861 - Multiple Issues with OCSP OCSP (mod_ssl) mishandles responses for responders in specific situations. For example, if a responder sends NULL or blank data but does not close the connection, mod_ssl unexpectedly ends the response. Further information about this issue is available at http://openssl.6102.n7.nabble.com/Decoding- OCSP-response-data-ASN1-D2I-READ-BIO-not-enough-data-td24437.html Additionally, OCSP does not work as expected when used in conjunction with an intermediate CA (Certification Authority), for example when a CA is used for Apache configuration. Further information about this issue is available at https://issues.apache.org/bugzilla/show_bug.cgi? id=46037 As a result of these problems, cretin OCSP responders do not work as expected with JBoss Enterprise Web Server and intermediary CAs also do not work as expected. These problems are fixed in JBoss Enterprise Web Server 2.0.1 using a patch. As a result of the fix, third party OCSP responders and intermediary CAs work as expected with JBoss Enterprise Web Server.