7. Issues fixed in this release
Following is a list of issues fixed in this release:
JBoss Application Server
- JBPAPP-2866: The JGroups protocol stack included an incorrect diagnostic address,
224.0.0.75
. The address has been corrected to224.0.75.75
. - JBPAPP-2306: The HP-UX init script in the First Customer Ship,
jboss_init_hpux.sh
, did not let users define a bind address with the-b
option. Support for this option has since been added to the script.
JBoss Messaging
- JBPAPP-2924: Between the First Customer Ship and General Availability releases of JBoss Enterprise Application Platform 5.0, the included version of JBoss Messaging was upgraded from 1.4.3 to 1.4.6 to provide better support for JBoss Enterprise Application Platform 5.0. For further information about the differences between JBoss Messaging 1.4.3 and JBoss Messaging 1.4.6, check the JBoss Messaging Release Notes.
JBoss Seam
- JBPAPP-2154: Some unsupported components such as IceFaces, Seam-jul and Wicket integration were included in the First Customer Ship. These unsupported components and the examples related to them have been removed.
- JBPAPP-2155: The Seam documentation included in the First Customer Ship contained unverified and unsupported information about non-JBoss containers. Unsupported information has been removed from the documentation, and the examples to do with unsupported containers have been removed.
JBoss Hibernate
- JBPAPP-2900: MySQL uses the
TEMPORARY
keyword to bypass implicit transaction commits. Previously, Hibernate used<CREATE TEMPORARY TABLE>
with<DROP TABLE>
. Omitting theTEMPORARY
keyword caused an implicit commit, and immediate failure within an XA Transaction.<DROP TEMPORARY TABLE>
is now supported and this issue no longer presents.
Documentation
- JBPAPP-2948: The
deploy/jmx-remoting.sar
service instantiates a JSR-160 adapter for standardized remote access to the JBoss MBeanServer. This service is used with tools such as the JConsole. At present, this service does not support secure access. In production environments where the server binds to a specific address other thanlocalhost
this presents a potential security risk, so the adapter has been moved from thedeploy
directory intodocs/examples/jmx
. We do not recommend enabling it for production usage. If during development you wish to re-enable the adapter, copy it back to thedeploy
directory.The adapter has been moved to/docs/examples
. If you wish to re-enable it, move it back to thedeploy
directory.