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.3.0.CP01 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.0.CP01.
These release notes contain important information related to JBoss Enterprise Application Platform 4.3.0.CP01. 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 JBoss Enterprise Application Platform 4.3, 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.0.CP01, 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.
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-731: Update sample-bindings.xml with JBoss Messaging values.
JBPAPP-723: Ensure JBoss Messaging examples and documentation are up to date.
JBPAPP-720: Stateless example do not work with EAP 4.3.
JBPAPP-718: queue jboss messaging example does not work with eap 4.3.
JBPAPP-717: ejb3mdb example failes with EAP 4.3.
JBPAPP-716: distributed-topic messaging example fails under eap 4.3.
JBPAPP-677: UseXAForMessagePull is always false.
JBPAPP-674: Daily counters increment on timer regardless of whether messages are sent.
JBPAPP-656: Upgrade JBoss Messaging to 1.4.3_cp02.
JBPAPP-649: ip_ttl for control channel is different to ip_ttl for data channel.
JBPAPP-648: ResultSet and PreparedStatement not explicitly closed in JDBCPersistenceManager.
JBPAPP-647: Clustered attribute is not updated on destination redeployment.
JBPAPP-646: The messaging bridge does not correctly handle JMSXProperties.
JBPAPP-645: Contention in getting transaction ids.
JBPAPP-640: JBM: Closing connection does not delete associated TemporaryQueues.
JBPAPP-581: ResultSet and PreparedStatement not explicitly closed in JDBCPersistenceManager.
JBPAPP-549: Memory Leak in MessagingXAResource within JBossMessaging.
JBPAPP-533: Typing error in the JBoss Messaging Guide.
JBPAPP-531: Grammar problem in JBoss Messaging documentation.
JBPAPP-530: Typing error in the JBoss Messaging Guide.
JBPAPP-521: Update cache invalidation using jms bridge.
JBPAPP-484: message.getJMSDestination() returning an invalid destination after the message has been delivered through a clustered topic.
JBPAPP-418: EJB3 testsuite fails.
JBPAPP-690: Upgrade JBoss Cache to 1.4.1.SP9.
JBPAPP-583: Enabling UseInterceptorMbeans in JBossCache is broken.
JBPAPP-582: Removal of Pojo in Collection loaded from CacheLoader returns a cleared Pojo.
JBPAPP-680: JBossWS init-param for handler defined in jaxrpc-config not processed
JBPAPP-458: Upgrade to JBC release with JBCACHE-1225 fixed.
JBPAPP-655: Update Remoting to 2.2.2.SP7.
JBPAPP-629: Remoting Connection's ObjectName hardcoded in org.jboss.ejb3.ProxyFactoryHelper.
JBPAPP-628: Remoting Connection's clientConnectAddress ignored under certain circumstances
JBPAPP-605: -b 0.0.0.0 caused InstanceNotFoundException during JBoss shutdown
JBPAPP-575: WSDL To Java - All generated types have first character upper case, extends clause in base types do not take this into account.
JBPAPP-574: WSDL to Java - Incorrect case of generated type for anonymous type.
JBPAPP-573: WSDL To Java - When an array is returned from a method on the SEI it is incorrectly ommitted from the generated JAX-RPC mapping.
JBPAPP-572: Release and upgrade to JBossWS 2.0.1.SP2_CP01.
JBPAPP-487: Error in: <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="off" />.
JBPAPP-781: Seam JPA example throws com.sun.facelets.FaceletException: .... .SeamExpressionFactory
JBPAPP-775: Seam JPA example throws com.sun.facelets.FaceletException: .... .SeamExpressionFactory
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-765: DVDStore example - entityManager is null exceptions
JBPAPP-762: Seam Booking example failure with javax.el.ELException: /register.xhtml @78,78 value="#{register.verify}"
JBPAPP-760: seamejb3/jsfejb3 GSG examples fail
JBPAPP-753: Documenation JSF/Seam examples package the wrong version of Seam
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-659: After logout from Seam test application the menu item with required login is not hidden.
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-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-611: SEAM Reference Guide desribes use with AS 4.0.5 not 4.2.0.
JBPAPP-554: SEAM Reference Guide for JBEAP 4.3 does not have English author credits.
JBPAPP-553: SEAM Reference Guide for JBEAP 4.3 has missing entities for YEAR and HOLDER.
JBPAPP-773: rh-eap-docs RPM epoch mismatch relating to Hibernate javadoc.
JBPAPP-739: Upgrade Hibernate to 3.2.4.SP1_CP03
JBPAPP-727: Update JBossTS to 4.2.3 SP5 CP01 in EAP 4.2 CP03/EAP 4.3 CP01.
JBPAPP-566: Change the default configuration of transaction timeout handling.
JBPAPP-564: Update xa_prepare transaction error handling.
JBPAPP-562: Missing transaction recovery for xa-datasources in app server.
JBPAPP-806: SSLSessionInterceptor has a copy/paste error in the invokeHome method.
JBPAPP-778: Production default logging is too verbose for a production environment.
JBPAPP-768: EAP 4.3 GUI installer suggests EnterprisePlatform-4.2.0.GA_CP01 as the default destination path.
JBPAPP-767: Difference between some files in the zip distribution of EAP and the svn sources.
JBPAPP-750: Failure of the org.jboss.test.jca.test.ExecuteJMSDuringRollbackStressTestCase.
JBPAPP-749: server-config-guide - Sample Bindings example not working.
JBPAPP-732: JBossWS - OWASP A6: Information leakage by unprotected servlets.
JBPAPP-726: JCA WorkManager transaction timeouts incorrectly handled with milliseconds and seconds being confused.
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-707: Use of <depends> on 2.1 MDB to control enabling/disabling consumption leads to NPE.
JBPAPP-705: test-bridge-service.xml throws exceptions when deploying.
JBPAPP-704: failing WebIntegrationUnitTestCase - OOME.
JBPAPP-696: WSDL To Java, add a configuration option so all generated types can implement java.io.Serializable.
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-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-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-680: JBossWS init-param for handler defined in jaxrpc-config not processed
JBPAPP-678: Fix JMSTransportSupport Test Case
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-675: ServerPeer should be defined as a System property.
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-662: Transaction status on SQL operations.
JBPAPP-661: ASPATCH-222: Add JBAS-4453 add column class to the SerializableResultSetMetaData.
JBPAPP-660: Remove Odd Numbers/Letters From Release Filenames.
JBPAPP-658: Twiddle not displaying info regarding java.lang:* beans when -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl is used.
JBPAPP-654: The tests-webservice-ssl target is now removed from testsuite/build.xml completely.
JBPAPP-650: The default JAXWS configuration should have returned transfer encoding enabled, which it didn't. This leads to OutOfMemory errors, because the HTTP connector then uses double buffering.
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-632: Upgraded to JGroups so that subtask JIRAs are fixed for the next EAP releases.
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-607: Added parseRoleNameFromDN option to LdapExtLoginModule.
JBPAPP-606: The JSP compiler will now compile JDK 1.5 source by default.
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-593: Missing quotes in run.sh script.
JBPAPP-592: Created test for NoInitialContextException on deployment of EAR that contains MDB and persistence.xml.
JBPAPP-590: Remove JBossAS community release notes from EAP 4.2.
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-577: A NullPointer occurs during server shutdown when using JBoss AOP.
JBPAPP-570: Add support perspective of JTS/XTS to EAP4.x doc.
JBPAPP-569: Unable to run JBoss AS on IBM jdk - passing -server option.
JBPAPP-567: Patch for [JBAS-4969] for EAP 4.3.
JBPAPP-559: CLONE -TransactionSynchronizationRegistry should not be in JTA 1.0.
JBPAPP-546: LoadBalancePolicy that tries to pin all requests associated with a tx to one server.
JBPAPP-544: OWASP A6: Information leakage by unprotected servlets.
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-499: The JFreeChart component before 1.0.8 is vulnerable to Cross-Site-Scripting when generating imagemaps.
JBPAPP-381: javax.ejb.NoSuchEJBException occurs when using SFSB buddy replication.
JBPAPP-355: Merge JBAS-4698 into the next CP. This effectively fixes the oswego library. Several defects were found, including an unthreadsafe call to toArray()..
JBPAPP-344: The rh-eap-examples rpm needs to be packaged into the ISO..
JBPAPP-155: J2EE Compatbility: Compliance issues affecting the Enterprise Application Platform..
JBPAPP-3: AS 4.2 Clustering Guide information - included in the Server Configuration Guide now..