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.0 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.0 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.0 GA installations.
This guide contains the following chapters:
Chapter 1, Release Notes: this chapter contains the release notes.
The following conventions are used in this guide:
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.
Table 1 Formatting Conventions
In addition to this guide, the following guides are available in the JBoss ESB 4.0 GA documentation set:
JBoss ESB 4.0 GA Trailblazer Guide: Provides guidance for using the trailblazer example.
JBoss ESB 4.0 GA Getting Started Guide: Provides a quick start reference to configuring and using the ESB.
JBoss ESB 4.0 GA Programmers Guide: How to use JBossESB.
JBoss ESB 4.0 GA Administration Guide: Information on how to manage the ESB.
JBoss ESB 4.0 GA Services Guides: Various documents related to the services available with the ESB.
Questions or comments about JBoss ESB 4.0 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 September 2006
vsftpd, Cerberus and proftpd
The system may work with other versions of the platforms.
The following enhancements have been made to the GA version of JBossESB since the last early access release:
There have been significant changes to the architecture of JBossESB since the Beta release. You should consult the Programmers Guide for more information.
JBossESB now supports a Transformation Service, a Message Storage Service, a Content Based Routing Service and a Registry Service. Full details of these individual services can be found in the Programmers Guide or the respective services' guides.
The trailblazer has been updated to illustrate the new features in JBossESB.
A number of other examples have been added to show the individual capabilities within JBossESB more clearly.
The configuration files have been rationalised and normalised. They are now supported by an annotated XSD for strong type-checking. We recommend that you use this new approach to configuration rather than the style used in previous releases (which is still supported). If used in conjunction with an XML editor, such as that provided by Eclipse, then creating configuration files for JBossESB should be a lot less error prone.
The following issues in the RC have been fixed in the GA:
[JBESB-357] – There was a problem with the SAR deployment and threads which caused problems when running with JBossAS.
[JBESB-131] - Mixing directory separator fails on Windows
[JBESB-146] - purge rule for ant in trailblazer does not remove class files.
[JBESB-155] - loanbrokerRequestDir and loanbrokerEmailTemplatePath need to be dynamically configured with the loanbroker configure ant task
[JBESB-157] - Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time
[JBESB-163] - Install dir not copied into distribution
[JBESB-175] - package.html in transform package
[JBESB-178] - ModulePropertyManager appears to be loading the same properties file over and over again
[JBESB-179] - ModulePropertyManager doesn't seem to report any error when it fails to locate the properties file in question...
[JBESB-194] - Trailblazer configuration script needs to support being run from both an SVN checkout and a distro download
[JBESB-250] - Listeners fail after a lengthy period of being active.
[JBESB-256] - An explicit Thread.sleep should not be required between starting the message aware listeners, and starting the gateway listeners
[JBESB-262] - Service dependency - recover capability. (i.e. Gateways -> Listener dependency)
[JBESB-278] - Remove MC and EJB3 jars when deploying the console to the JBoss AS
[JBESB-281] - The Transformation Service console now runs on HSQL.
[JBESB-289] - Recovery does not stop warning messages
[JBESB-298] - URL parsing in EdtFtpImpl.checkParms()
[JBESB-305] - Document reference incorrect
[JBESB-306] - Formatting error in RegistryConfiguration document.
[JBESB-307] - Misleading text
[JBESB-313] - MBeans need to be added for SAR deployment based on new ListenerManager code
[JBESB-314] - JMS Bank sending reply exception
[JBESB-315] - The listener and gateway config files are written in the wrong order
[JBESB-316] - Classloader issues on sar redeployment
[JBESB-320] - Initial deployment of the sar reports an NPE on the console
[JBESB-330] - Missing jar file prevents sar deployment in helloworld_ftp_action
[JBESB-342] - waits to circumvent race conditions tests.
[JBESB-343] - Tests should clean up after themselves.
[JBESB-356] - Fix Trailblazer document
[JBESB-360] - Empty docs directory in trailblazer
[JBESB-380] - Custom composer for GatewayListeners not working
[JBESB-391] - sometimes the parser is not found when doing a parameter reload.
[JBESB-392] - smooks in sar does not work
[JBESB-395] - More SAR classloader woes :-)
[JBESB-397] - AdministrationGuide.pdf - refers to CR2
The following issues are known and within JIRA:
Gateway listeners cannot be registered under the same name as their ESB-aware counterparts. (http://jira.jboss.com/jira/browse/JBESB-280).
There is an issue with the Registry which means that all service-category names and service names must be unique for registered services.
Only Postgres and HSQL have been tested with the JDBC listener framework.
Not all FTP servers or configurations give suitable access for the FTP courier implementation. We are currently looking into how to improve support in this area. The FTP server that ships with Mac OS X is one we do not support.
When the application server is restarted within a running ESB deployment, you may see the a stack trace from the Connection Monitor Thread (http://jira.jboss.com/jira/browse/JBESB-312). This can be ignored. It will be fixed in a subsequent release of JBossESB.