4. Changes and Resolved Issues

In this release of JBoss Web Server, the Apache HTTP Server mod_snmp module has been replaced with mod_bmx. mod_bmx retrieves the same information about Apache HTTP server for external monitoring, and uses a HTTP/1.1 REST-like interface instead the SNMP protocol.

The following exception was displayed when JSP page was accessed with java.util.HashMap reference:

JDK8 JasperException: Unable to compile class for JSP. type java.util.Map$Entry

JDK8 JasperException: Unable to compile class for JSP. type java.util.Map$Entry

This issue was related to JDK 8. The HashMap implementation had changed and jasper works with HashMap$Entry subclass which is not present in the JDK 8 HashMap.

This issue is resolved in this release of JBoss Web Server 3, JSP pages with java.util.HashMap references should compile successfully.

An incompatibility problem existed with Apache HTTP Server and OpenSSL on Red Hat Enterprise Linux 6.5.

This resulted in no TLSv1.1 or TLSv1.2 options being available for Apache HTTP Server’s SSLProtocol directive.

This issue has been fixed with the update of OpenSSL to version 1.0.1e in this release of JBoss Web Server, and TLSv1.1 and TLSv1.2 options should be available as expected on all supported platforms.

The Apache HTTP Server mod_substitute module was missing in the Microsoft Windows build of JBoss Web Server.

This has been fixed in this release, and mod_substitute is now included in the Microsoft Windows build of JBoss Web Server 3.

Previously Hibernate had an issue in which EntityManager.flush() did not behave properly with a transient one-to-one association and no cascade. In this situation it is expected that an IllegalStateException will be thrown by the flush operation and the transaction marked for rollback, or the transaction commit will fail.

This issue has been fixed in this release of JBoss Web Server by upgrading Hibernate to 4.2.18.Final-redhat-1, and EntityManager.flush() operations will now behave as expected in situations of a transient one-to-one association and no cascade.

When using Java 8 features in JSP pages with Tomcat, JSP compiler exceptions similar to the following were thrown: Unable to compile class for JSP.

This issue occurred because the ECJ included with Tomcat 7 and 8 did not properly compile Java 8 classes.

This issue is fixed with the upgrade of ECJ to version 4.4 for both Tomcat 7 and 8, and Java 8 features in JSP pages should now compile successfully.