JBoss Enterprise Application Platform 4.2.0.CP02
Copyright © 2008 Red Hat, Inc
Copyright © 2008 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License (which is presently available at http://creativecommons.org/licenses/by-nc-sa/3.0/).
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other countries.
All other trademarks referenced herein are the property of their respective owners.
The GPG fingerprint of the security@redhat.com key is:
CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E
1801 Varsity Drive
Raleigh, NC 27606-2072
USA
Phone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
PO Box 13588
Research Triangle Park, NC 27709
USA
Abstract
These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP02 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.2.0.CP02.
These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP02. 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.
This section contains information related to installing or upgrading to JBoss Enterprise Application Platform version 4.2.0.CP02, 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.jboss.com/products/platforms/application/testedconfigurations. Refer to the installation guide available online from http://www.redhat.com/docs/manuals/jboss for detailed instructions to install and verify JBoss Enterprise Application Platform.
Using CSP/JON
Refer to https://network.jboss.com/confluence/display/DOC/Installing+a+Patch for instructions on installing a Cumulative Patch.
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.
Warning
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.
Note
Seam version used in this release is 1.2.1.GA.
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.
SRPMs
Source ZIP
Support Processes
http://www.redhat.com/support/process/
Production Support Scope of Coverage
http://www.redhat.com/support/policy/soc/production
Production Support Service Level Agreement
http://www.redhat.com/support/policy/sla/production/
Developer Support Scope of Coverage
http://www.redhat.com/support/policy/soc/developer/
Developer Support Service Level Agreement
http://www.redhat.com/support/policy/sla/developer/
Product Update and Support Policy by Product
http://www.redhat.com/security/updates/jboss_notes/
JBoss End User License Agreement
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 Guideexplains how to install and verify the installation of JBoss Enteprise Application Platform using different installation modes.Getting Starteddetails 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 Guideexplains 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.
JSR-181 related functionality is not supported in this version of the JBoss Enterprise Application Platform. This functionality is supported in version 4.3.
Following is a list of issues fixed in this release:
JBPAPP-520: Fix
persistence.xmldeployment scope problemJBPAPP-514: CLONE - JBoss Cache leaks memory when used with
FAIL_SILENTLYoptionJBPAPP-513: PCACHE-58 - Removal of Pojo in Collection loaded from CacheLoader returns a cleared Pojo
JBPAPP-508: @OneToOne(mappedBy might fail depending on alphebetical order
JBPAPP-487: <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="off" /> doesn't work.
JBPAPP-482: Logging for com.arjuna and org.hibernate needs to be curtailed for production config
JBPAPP-441: Upgrade to JBoss Cache 1.4.1.SP8
JBPAPP-438: DataGravitatorInterceptor logs ERROR when alone in cluster
JBPAPP-419: Leak in org/jboss/mx/loading/UnifiedClassLoader3 JMX Notifications
JBPAPP-415: Address in WSDL - Port value is -1 when server is requested with default port 80
JBPAPP-411: RPM Installed Init Script Incorrectly Configures Overide UDP Port Setting
JBPAPP-410: Transaction failover authorisation is broken within UnifiedInvokerHAProxy
JBPAPP-394: JBossCacheWrapper should not re-use data gravitation option
JBPAPP-392: ConsumerContainer throws NoInitialContextException on stop
JBPAPP-387: jms server failover with tibco ems
JBPAPP-379: HTTP session replication failover failures with async buddy replication
JBPAPP-374: Update exception handling in Remoting servlet transport
JBPAPP-371: Web session data gravitation can fail when backup node is slow to respond
JBPAPP-366: AJP Connector Threads Hang in
CLOSE_WAITStatusJBPAPP-363: Configurable JSESSIONID Cookie Name
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-357: HHH-2542 - NullPointerException in TypeFactory.replaceAssociations for ComponentType
JBPAPP-356: InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
JBPAPP-355: Merge JBAS-4698 into the next CP. This effectively fixes the oswego library. Several defects were found.
JBPAPP-353: Upgrade JBoss Remoting version to 2.2.2.SP4
JBPAPP-351: JBossAOP - Undeployment results in NullPointerException
JBPAPP-341: Include the CSIv2-patched JacORB
JBPAPP-335: local interface looked up remotely if identical deployments on local and remote instances
JBPAPP-334: Upgrade JBossCommon 1.2.1.GA
JBPAPP-329: Upgrade version of HSQLDB used to match community version
JBPAPP-310: JBossCache - Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
JBPAPP-306: JBCACHE - Memory leak in PojoCache undo list
JBPAPP-305: JBCACHE- Setting Option ineffective if CacheLoader or BuddyReplication is used
JBPAPP-303: Preload commons logging in web container to avoid container/application interactions
JBPAPP-407: DOMUtils doesn't clear thread locals. This will cause a memory leak.