Copyright © 2007 Red Hat, Inc.
Abstract
These release notes contain important information related to JBoss Enterprise Application Platform 4.3 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.3.
These release notes contain important information related to JBoss Enterprise Application Platform 4.3. New features, known problems, resources, and other current issues are addressed here.
JBoss Enterprise Application Platform is the next evolutionary step in open source enterprise software. It is a powerful tool for developing rich, high performance, Web 2.0 applications on a pure Java Platform.
JBoss Enterprise Application Platform provides complete compatibility with existing J2EE 1.4 enterprise Java applications. At the same time, almost all the key features and components defined in the Java EE 5.0 specification are supported. So your new enterprise Java applications can take immediate advantage of the Java EE 5.0's significantly simpler POJO-based programming model.
Further, by integrating best-of-breed open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of innovations in the open source community. As well, JBoss Enterprise Application Platform is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.
All of which means you can develop your new application taking advantage of Java EE 5.0 technologies immediately and with the confidence of knowing it will remain forward-compatible with future versions of the JBoss Platform.
In this release, JBoss MQ 1.3 has been replaced with JBoss Messaging 1.4. JBoss Messaging provides a high performance messaging infrastructure for JBoss Enterprise Application Platform.
This section contains information related to installing or upgrading to JBoss Enterprise Application Platform version 4.3, including hardware and platform requirements and prerequisites.
You must have adequate disk space to install JDK and JBoss Enterprise Application Platform while also allowing enough space for your applications. You must have a working installation of JDK 1.5. For the latest information on supported Operating System / JVM combinations, supported Database platforms and current information on the revision level of included components, please refer to http://www.redhat.com/jboss/platforms/application/.
JBoss MQ is now replaced with JBoss Messaging as the JMS implementation shipped within JBoss Enterprise Application Platform 4.3. Since JBoss Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS code written against JBossMQ will run with JBoss Messaging without any changes.
JBoss Messaging only runs with Java 5 or later. It does not have wire format compatibility with JBoss MQ. Even though JBoss Messaging deployment descriptors are very similar to JBoss MQ deployment descriptors, they are not identical. Also, the database data model is completely different, so don't attempt to use JBoss Messaging with a JBoss MQ data schema and vice-versa.
Refer to the JBoss Messaging User Guide for more information.
It is recommended to run the example Seam applications that are included with the documentation using the production configuration. Using another configuration may result in memory issues. Note that the default configuration for the server to start with, if no other configuration is specified, is the production configuration.
To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating JAVA_OPTS settings in the file JBOSS_DIST/jboss-as/server/production/run.conf with these recommended values:
-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m
Refer to the "Seam Reference Guide" included in the documentation set (JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf) for important information regarding the deployment of Seam examples and detailed information on developing applications using Seam.
If you are using the rpm, or the zip distribution, please note that by default, authentication is enabled and no user accounts are set up. This is done to prevent unauthorized access to various services of JBoss AS. Please refer to the Installation Guide, or see http://kbase.redhat.com/faq/FAQ_107_9963.shtm for information on how to make the services accessible again.
Hypersonic SQL provides default "out of the box" database functionality for evaluation and development use only. It is NOT recommended or supported as a production-use database. Technical support is not available for this component, and while we are happy to accept bugs filed against this component, we do not make any commitment to fix them within a specific timeframe.
http://www.redhat.com/support/process/
http://www.redhat.com/support/policy/soc/production
http://www.redhat.com/support/policy/sla/production/
http://www.redhat.com/support/policy/soc/developer/
http://www.redhat.com/support/policy/sla/developer/
http://www.redhat.com/security/updates/jboss_notes/
Refer to the index.html file in the documentation directory for a list of included documentation.
In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, jboss-eap-docs-<version>.zip.
On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are jboss-seam-docs-<version>.noarch.rpm, and rh-eap-docs-<version>.noarch.rpm. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at http://kbase.redhat.com/faq/FAQ_35_198.shtm
Installation Guide explains how to install and verify the installation of JBoss Enteprise Application Platform using different installation modes.
Getting Started details the directory structure of the platform and a quick tour of the Application Server and different configuration sets and services. Using a simple web application it illustrates the use of JSF-EJB3 components and how to use Seam to integrate the JSF and EJB3 components.
Server Configuration Guide explains all administrative and configuration functions in detail.
Updated versions of the documentation with errata and additional information, example application code, as well as the most recent version of the release notes may be accessed via the web from http://www.redhat.com/docs/manuals/jboss.
Following is a list of issues fixed in this release:
JBPAPP-367 & JBPAPP-503: In this release JBoss Messaging 1.4.0.SP3 is used as the Java Message Service (JMS) provider instead of JBoss MQ.
JBPAPP-238: JBoss Web Services is upgraded to 2.0.1 in this release and will now provide a complete implementation of JAX-WS.
JBPAPP-441: JBoss Cache has been upgraded to version 1.4.1.SP7, which includes the following fixes:
JBPAPP-310: JBossCache does not handle STATUS_UNKNOWN transaction outcomes, which can leave resources locked.
JBPAPP-306: Memory Leak in the PojoCache undo list.
JBPAPP-305: BuddyReplication with autoDataGravitationEnabled=false does not work correctly if a CacheLoader is configured.
JBPAPP-454: TreeCache._enqueueMethodCall doesn't handle buddy backup FQNs.
JBPAPP-438: DataGravitatorInterceptor logs ERROR when alone in cluster.
JBPAPP-371: Web session data gravitation can fail when backup node is slow to respond.
JBPAPP-353: Remoting has been upgraded to version 2.2.2.SP4 from 2.2.2.GA, which includes the following fixes:
JBPAPP-374: ServletServerInvoker returns an error message instead of an entire serialized exception, which differs from the default behavior of other Server Invokers.
JBPAPP-402: Under certain conditions in JBoss Remoting an infinite loop can occur which causes createQueueConnection to hang.
JBPAPP-497: JBossWeb upgraded to 2.0.0.GA_CP05.
JBPAPP-423: There is an error logged for each request which comes through AJP connector.
JBPAPP-494: JBoss Seam remoting issue with Seam 1.2.1.AP. When running the Seam chat room example an exception is thrown by the remoting poller code - "No application context active".
JBPAPP-475: Seam chatroom example - JMS related errors.
JBPAPP-253: A bug in run.sh prevents the platform from starting up if -c command line arguments is 10 or more arguments down in the list.
JBPAPP-254: In the Clustered Console's web.xml file, the system property used to describe the multicast port for HA cluster partition is wrong.
JBPAPP-482: Logging for com.arjuna and org.hibernate should be set to INFO and not DEBUG for production configuration.
JBPAPP-456: JMS server failover with tibco ems.
JBPAPP-444: "bind_to_all" attribute set to true for MPING protocol of messaging data channel JGroups stack configuration.
JBPAPP-419: Leak in org/jboss/mx/loading/UnifiedClassLoader3 JMX Notifications.
JBPAPP-410: Transaction failover authorisation is broken within UnifiedInvokerHAProxy.
JBPAPP-394: JBossCacheWrapper should not re-use data gravitation option.
JBPAPP-393: EAP 4.3 is not discovered by JON 1.4.31 (SP2).
JBPAPP-392: ConsumerContainer throws NoInitialContextException on stop.
JBPAPP-379: HTTP session replication failover failures with async buddy replication.
JBPAPP-361: WebService ignores java.rmi.server.codebase system property.
JBPAPP-360: Re-enable JGroups message bundling.
JBPAPP-359: Upgrade to JGroups 2.4.1.SP4.
JBPAPP-349: Create a generic way to createDestinations on MDB Container.
JBPAPP-341: Include the CSIv2-patched JacORB.
JBPAPP-334: JBossCommon upgraded to version 1.2.1.GA.
JBPAPP-329: Upgrade version of HSQLDB used to match community version.
JBPAPP-303: Preload commons logging in web container to avoid container/application interactions.
JBPAPP-263: EJBTHREE-942 support RemoteBindings annotations from ejb3-interceptors-aop.xml.
JBPAPP-262: If the installation path contains space(s), JPA fails.
JBPAPP-261: EJBTHREE-1022 - system properties replacement for sub-values.
JBPAPP-260: EJBTHREE-975 - HA-JNDI InitialContext for @Resource annotation.
JBPAPP-259: EJBTHREE-997 - implement and create test for security-role-ref.
JBPAPP-258: Hibernate annotations - Guaranty the same parameter ordering when overriding SQL across VMs and compilations.
Following is a list of known issues at the time of release. Further details on these issues can be found in JIRA.
JPBAPP-351: During server shutdown, a NullPointerException occurs when using JBossAOP.