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
These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP03 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.CP03.
These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP03. 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.CP03, 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.
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.
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.
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.
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.
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-785: Remove JUnit and JBPM/BPEL From The EAP Distribution
JBPAPP-781: Seam JPA example throws com.sun.facelets.FaceletException: .... .SeamExpressionFactory
JBPAPP-775: Seam JPA example throws com.sun.facelets.FaceletException: .... .SeamExpressionFactory
JBPAPP-773: rh-eap-docs RPM epoch mismatch relating to Hibernate javadoc
JBPAPP-767: Difference between some files in the zip distribution of EAP and the svn sources
JBPAPP-766: In the Seam component of the EAP the DVDStore example contains a switch order process that does not seem to do anything
JBPAPP-753: Documenation JSF/Seam examples package the wrong version of Seam
JBPAPP-749: server-config-guide - Sample Bindings example not working
JBPAPP-747: server-config-guide - JMS examples not working
JBPAPP-739: Upgrade Hibernate to 3.2.4.SP1_CP03
JBPAPP-737: JBossWS - Explode jbossws-context.war
JBPAPP-733: JBossWS - OWASP A6: Information leakage by unprotected servlets
JBPAPP-727: Upgrade JBossTS in EAP to 4.2.3 SP5 CP01.
JBPAPP-725: The units in which transaction timeout intervals are counted in the JCA are incorrect. Milliseconds and seconds are confused, leading to incorrect timeout handling.
JBPAPP-724: Revert JChannel auto_getstate and auto_reconnect default values to false.
JBPAPP-715: Added the ability to change the partition name of the cluster test partition and to limit autodiscovery to that partition for cluster testsuite HA-JNDI clients
JBPAPP-714: quartz-all.jar file needs to be added to the distribution.
JBPAPP-709: JBAS-5331 - AOP deployer should include pluggable instrumentor jar(s)
JBPAPP-708: Enterprise Hibernate standalone application supporting JDK 1.5
JBPAPP-707: Use of <depends> on 2.1 MDB to control enabling/disabling consumption leads to NPE
JBPAPP-704: failing WebIntegrationUnitTestCase - OOME
JBPAPP-701: Prepare Hibernate for EAP 4.2 CP03
JBPAPP-694: Patch for EJBTHREE-1190 and EJBTHREE-1191 in relation to the Application Server
JBPAPP-692: Update License type for jUDDI
JBPAPP-691: JBCACHE-1292 - endless loop on concurrent remove.
JBPAPP-690: Upgrade JBoss Cache to 1.4.1.SP9
JBPAPP-689: Twiddle will use automatic discovery to find the server if an incorrect URL is specified on the command line leaving users confused as to the server that reported the results.
JBPAPP-688: Transaction timeout is not raising a JMSException in the JBossMQ Persistence manager or StateManager.
JBPAPP-687: JmsActivation reconnection could start multiple threads.
JBPAPP-686: The JBossMQ UIL2 Read/Write tasks both do their stream initialization when each thread starts. This code needs changing such that the streams are allocated before starting the threads.
JBPAPP-685: JBossMQ WriteTask in UIL2 could block forever.
JBPAPP-684: JMS and EJB3 Fixes including a fix to address NoInitialContextException on deployment
JBPAPP-683: JBAS-5226 - ClientUserTransaction should be configured with Unified invoker.
JBPAPP-682: CVE-2008-1285 XSS vulnerability in glassfish-jsf.
JBPAPP-681: ASPATCH-236: Adding Few more Filter options for TCLFilter.
JBPAPP-679: myfaces libraries were deleted from Seam and JSF RI from Sun were added, also examples were changed for using JSF 1.2
JBPAPP-676: removed commons-digester-1.6.jar, commons-beanutils-1.7.0.jar and commons-lang-2.1.jar from examples booking, ui, spring, icefaces (only commons-digester-1.6.jar). The example build files to copy these files from global lib directory instead of being copied from resources\WEB-INF\lib as also been changed.
JBPAPP-673: jfreechart and jcommon packages do not own unversioned javadoc link
JBPAPP-672: Port ASPATCH-299 into EAP branch.
JBPAPP-669: RMI Client Doesn't Always Immediately Recover After Complete Cluster Shutdown
JBPAPP-667: On undeploy use JBC remove() with local-only option to clean out sessions.
JBPAPP-666: External persistence contexts tested.
JBPAPP-665: Verify the application of ASPATCH-251 (EJBTHREE-1023).
JBPAPP-664: JMS provider removes the subscriber, when it still has unacknowledged messages
JBPAPP-663: Redelivery flags not updated in case of JBossMQ node failure
JBPAPP-661: ASPATCH-222: Add JBAS-4453 add column class to the SerializableResultSetMetaData.
JBPAPP-660: Remove Odd Numbers/Letters From Release Filenames.
JBPAPP-659: After logout from Seam test application the menu item with required login is not hidden.
JBPAPP-655: Update Remoting to 2.2.2.SP7.
JBPAPP-654: The tests-webservice-ssl target is now removed from testsuite/build.xml completely.
JBPAPP-651: Wrong cglib jar released with EAP 4.2 CP01 and CP02.
JBPAPP-641: When the testsuite is run on Z-systems with IBM 1.5 JDK, the roles form the XML file loaded in backwards order. The testcase assertion has now been changed to fix this.
JBPAPP-638: Adding a page security element in a generate Seam Project gets into an infinite loop.
JBPAPP-637: library lib/jsf-facelets.jar was upgraded to the stable version
JBPAPP-636: libraries ajax4jsf-1.1.1.jar and richfaces-3.0.1.jar were upgraded to the stable release versions from SNAPSHOT versions
JBPAPP-634: Old JFreeChart Jar included in Seam
JBPAPP-632: Upgraded to JGroups so that subtask JIRAs are fixed for the next EAP releases.
JBPAPP-631: Using the Seam New Project Wizard and generating a new project results in a problem. This is now rectified in this CP release.
JBPAPP-629: Remoting Connection's ObjectName hardcoded in org.jboss.ejb3.ProxyFactoryHelper
JBPAPP-628: Remoting Connection's clientConnectAddress ignored under certain circumstances
JBPAPP-626: SSLFailuresSocketsUnitTestCase and SSLSocketsUnitTestCase fail with IBM JDK
JBPAPP-624: switched to use Remoting 2.2.2.SP5
JBPAPP-623: jmx-console displayed blank InvocationStatistics
JBPAPP-621: NPE for EntityManager injection in @PostConstruct
JBPAPP-612: Verify the RHN Installation method description in the Installation Guide
JBPAPP-611: SEAM Reference Guide desribes use with AS 4.0.5 not 4.2.0
JBPAPP-607: Added parseRoleNameFromDN option to LdapExtLoginModule
JBPAPP-606: The JSP compiler will now compile JDK 1.5 source by default.
JBPAPP-605: -b 0.0.0.0 caused InstanceNotFoundException during JBoss shutdown
JBPAPP-604: Didn't used to find the good persistence unit when multiple ear with same pu name
JBPAPP-602: jsfejb3 example application was already built in the binary distribution so the ant task to build it looked like it did not do anything.
JBPAPP-600: Getting started guide did not describe how to build the seamejb3 example - inconsistent with jsfejb3 example
JBPAPP-599: In order to log into the issues tracker example application you had to look through the import.sql file in the resources directory so you could find the user names and passwords
JBPAPP-594: jsfejb3 and seamejb3 examples deployment information was not correct in the getting started guide
JBPAPP-593: Missing quotes in run.sh script
JBPAPP-592: Created test for NoInitialContextException on deployment of EAR that contains MDB and persistence.xml
JBPAPP-589: org.jboss.test.security.test.HttpsUnitTestCase failing with the IBM jvm
JBPAPP-586: BMT to CMT w/container managed EPC does not propagate
JBPAPP-585: A bean injecting an EntityManager with no corresponding persistence context is quietly ignored
JBPAPP-576: Release and upgrade to JBossWS 1.2.1.GA_CP03
JBPAPP-570: Add support perspective of JTS/XTS to EAP4.x doc
JBPAPP-567: Patch for [JBAS-4969] for EAP 4.3
JBPAPP-565: change transaction timeout handling default config
JBPAPP-563: updated xa_prepare transaction error handling
JBPAPP-561: missing transaction recovery for xa-datasources in app server
JBPAPP-558: TransactionSynchronizationRegistry should not be in JTA 1.0
JBPAPP-554: SEAM Reference Guide for JBEAP 4.3 does not have English author credits
JBPAPP-550: NoInitialContextException on deployment of EAR that contains MDB and persistence.xml
JBPAPP-546: JBAS-4455 - LoadBalancePolicy that tries to pin all requests associated with a tx to one server
JBPAPP-542: Packages onwebqa not signed
JBPAPP-539: Unable to shutdown appserver instance running as service if JMX console secured.
JBPAPP-538: keyalias doesn't work correctly when an encrypted password is configured on SSL connector.
JBPAPP-443: Interceptor stack in NamingService-xmbean.xml doesn't work
JBPAPP-368: Make WS 1.2.1 compatible with changes to build with WS 2.0.x
JBPAPP-3: AS 4.2 Clustering Guide information - included in the Server Configuration Guide now