JBoss ESB 4.2 GA
The information contained in this documentation is subject to change without notice.
JBoss Inc. makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. JBoss Inc. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Java™ and J2EE is a U.S. trademark of Sun Microsystems, Inc. Microsoft® and Windows NT® are registered trademarks of Microsoft Corporation. Oracle® is a registered U.S. trademark and Oracle9™, Oracle9 Server™ Oracle9 Enterprise Edition™ are trademarks of Oracle Corporation. Unix is used here as a generic term covering all versions of the UNIX® operating system. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.
JBoss, Home of Professional Open Source Copyright 2006, JBoss Inc., and individual contributors as indicated by the @authors tag. All rights reserved.
See the copyright.txt in the distribution for a full listing of individual contributors. This copyrighted material is made available to anyone wishing to use, modify, copy, or redistribute it subject to the terms and conditions of the GNU General Public License, v. 2.0. This program is distributed in the hope that it will be useful, but WITHOUT A WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details. You should have received a copy of the GNU General Public License, v. 2.0 along with this distribution; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
JBoss ESB 4.2 GA
Restricted Rights Legend
Use, duplication, or disclosure is subject to restrictions as set forth in contract subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause 52.227-FAR14.
Table of Contents
About This Guide 5
What This Guide Contains 5
Documentation Conventions 5
Additional Documentation 6
Contacting Us 6
Release Notes 8
Fixed Issues 8
Known Issues 9
About This Guide
The Release Notes contains contain important information on changes to JBoss ESB 4.2 GA since the last release and information on any outstanding issues.
This guide is most relevant to engineers who are responsible for administering JBoss ESB 4.2 GA installations.
This guide contains the following chapters:
Chapter 1, Release Notes: this chapter contains the release notes.
In paragraph text, italic identifies the titles of documents that are being referenced. When used in conjunction with the Code text described below, italics identify a variable that should be replaced by the user with an actual value.
Emphasizes items of particular importance.
Text that represents programming code.
Function | Function
A path to a function or dialog box within an interface. For example, “Select File | Open.” indicates that you should select the Open function from the File menu.
( ) and |
Parentheses enclose optional items in command syntax. The vertical bar separates syntax items in a list of choices. For example, any of the following three items can be entered in this syntax:
persistPolicy (Never | OnTimer | OnUpdate | NoMoreOftenThan)
A note highlights important supplemental information.
A caution highlights procedures or information that is necessary to avoid damage to equipment, damage to software, loss of data, or invalid test results.
The following conventions are used in this guide:
Table 1 Formatting Conventions
In addition to this guide, the following guides are available in the JBoss ESB 4.2 GA documentation set:
JBoss ESB 4.2 GA Trailblazer Guide: Provides guidance for using the trailblazer example.
JBoss ESB 4.2 GA Getting Started Guide: Provides a quick start reference to configuring and using the ESB.
JBoss ESB 4.2 GA Programmers Guide: How to use JBossESB.
JBoss ESB 4.2 GA Administration Guide: Information on how to manage the ESB.
JBoss ESB 4.2 GA Services Guides: Various documents related to the services available with the ESB.
Questions or comments about JBoss ESB 4.2 GA should be directed to our support team.
JBossESB has been tested against the following platforms:
Linux FC6 and Windows XP Professional SP2
juddi trunk as of June 2007
vsftpd, Cerberus, PureFTPd and proftpd
The system may work with other versions of the platforms.
This is JBossESB 4.2 GA. As such it contains a number of enhancements, including:
JBossESB now supports WS-BPEL (through a partnership with ActiveEndpoints) and Web Services (through JBossWS 2.0.0GA).
There is now support for clustering and load balancing over arbitrary transports. This is a best-effort approach and should be suitable for many applications.
More of the Message header routing information is now being used; for example ReplyTo and FaultTo.
JBoss Messaging 1.3.0GA is now the default JMS implementation. This has significant performance and reliability benefits over the other supported JMS implementations.
Drools 4.0.1GA is the default Rules implementation.
We now support jBPM integration. Please consult the Programmers Guide for more information.
Support for OracleAQ is now available.
Services can now be scheduled to pick up messages. See the documentation for more details on this capability.
There have been many updates since the last milestone release. Please consult the separate text file on the downloads page that contains the complete list of issues closed against 4.2 GA.
The following issues are known and within JIRA:
At present JBossESB does not perform life-cycle monitoring of the services that are deployed within it. As such, if services fail or move elsewhere, their EPRs that may reside within the registry will remain until they are explicitly updated or removed by an administrator. Therefore, if you get warnings or errors related to EPRs obtained from the registry, you should consider removing any out-of-date items.
There is a bug in JBoss Messaging 1.3.0 GA (http://jira.jboss.com/jira/browse/JBMESSAGING-1064) which means that JMS message ids are being incorrectly changed when running within a cluster. For now we recommend that if correlation and clustering of JBoss Messaging are necessary, you use a custom correlation identifier within the body of the message.
http://jira.jboss.com/jira/browse/JBESB-748: FTP Couriers leak connections.
There are a number of minor issues with the quickstarts. Please check the JIRA pages for more details.