Chapter 2. Feature Requests

Clustering

https://issues.jboss.org/browse/JBPAPP-9167

The TCPPING configuration in JGroups had to statically define the list of all possible cluster members. Consequently, the cluster had to be restarted if a new member was added. The max_dynamic_hosts property has been added to TCPPING which defines the number of extra hosts to be added dynamically to the cluster without the need to restart the cluster. Therefore, it is now possible to add new members to the cluster when using TCPPING without requiring the cluster restart. The property default value is 0. Note that the new nodes need to be added statically to each node's configuration at the next restart of that node.

https://issues.jboss.org/browse/JBPAPP-9370

When JGroups caught an IOException while creating server sockets, the root exception was hidden and not included in the thrown exception. This way, users could not identify the cause of the error that occurred. The root exception is now included in the thrown exception so that users can identify the root cause of the error.

https://issues.jboss.org/browse/JBPAPP-9562

When a cluster member does not respond before timeout, other members can fail to join the cluster. Previously, in this case, the logs contained only an entry about the timeout event that occurred while waiting for responses from the cluster ("GMS flush by coordinator at <ip_address>:<port> failed ") and did not report which members were not present in the cluster. Now, the log level of this event was changed from DEBUG to WARN, and the log event contains a list of the missing cluster members to allow easier troubleshooting.

Documentation

https://issues.jboss.org/browse/JBPAPP-8223

The Installation Guide did not explicitly state that the latest security patches should be applied immediately after installation. This has now been added to the guide immediately following the installation instructions.

https://issues.jboss.org/browse/JBPAPP-9496

The Getting Started Guide has been restructured and simplified.

https://issues.jboss.org/browse/JBPAPP-5299

Information about how to enable LDAP integration with JBossWS has been added to the WS CXF User Guide book.

https://issues.jboss.org/browse/JBPAPP-5417

A section describing RoleMappingLoginModule and its configuration options has been added to the Security Guide.

https://issues.jboss.org/browse/JBPAPP-9299

Information on how to remove jsessionid numbers from an application's URL has been added to the Administration and Configuration Guide.

HornetQ

https://issues.jboss.org/browse/JBPAPP-8436

The messages export tool has been rewritten to support large messages in HornetQ. It can now export and import both the journal and large messages' content.

JCA

https://issues.jboss.org/browse/JBPAPP-8119

The JMS Java Connection Architecture's Resource Adapter has been enhanced to support javax.jms.ConnectionFactory and javax.jms.XAConnectionFactory.

Scripts and Commands

https://issues.jboss.org/browse/JBPAPP-8503

The jarcheck.sh, jarcheck.bat and jarcheck.jar scripts have been added to the JBOSS_HOME/bin directory. These scripts collect MD5 checksums of system JAR files to identify which of them have been changed after installation.

https://issues.jboss.org/browse/JBPAPP-7454

JBoss Enterprise Application Platform attempted to load a per-profile run.conf file from the default location in $JBOSS_HOME/server/$PROFILE. Consequently, per-profile run.conf files stored in a different location were not loaded. The --run-conf=... option (on Windows: -r) has been added to the run.sh script, allowing to specify the location of the run.conf file that sould be used. Using this option, per-profile run.conf files stored in another than the default location can now be loaded correctly.

Security

https://issues.jboss.org/browse/JBPAPP-8140

An enhancement has been made to JBoss Negotiation when configured as an authentication source. If a client authenticates to the server using a forwardable Kerberos ticket then the client's credentials can be accessed on the server using the JBoss Negotiation API and used for further calls (delegation using GSSAPI, WS-Kerberos, credential propagation for EJB calls, etc.).

https://issues.jboss.org/browse/JBPAPP-5882

Exposing the keystore or truststore password in JaasSecurityDomain is insecure. The getKey and getCertificate methods have been added to retrieve private keys and certificates directly from the JSD so that they can be used by external components. The getKey method requires you to provide a security token.

Web Services

https://issues.jboss.org/browse/JBPAPP-7977

In certain scenarios, JBossWS sends a large number of small packets over the network instead of sending a smaller number of larger packets. The following system property has been introduced in this release:

-Dorg.jboss.ws.domwriter.FlushOnlyOnce=true

If the value of the property is set to true, the size of packets sent over the network is increased and their number reduced.

https://issues.jboss.org/browse/JBPAPP-7452

JBossWS-CXF is used as the native stack for rewriting the soap:address values in WSDL definitions, except when a jbossws-cxf.xml file is provided in the web service's deployment. This enhancement allows the use of JBossWS-CXF even with the jbossws-cxf.xml file, by providing CXF-specific configuration in the file.

https://issues.jboss.org/browse/JBPAPP-7441

Web Services have been enhanced to allow wrapped style code generation with the xsd:extension of a wrapper-compatible type.