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 Milestone Release 1
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 Milestone Release 1 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 Milestone Release 1 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 Milestone Release 1 documentation set:
JBoss ESB 4.2 Milestone Release 1 Trailblazer Guide: Provides guidance for using the trailblazer example.
JBoss ESB 4.2 Milestone Release 1 Getting Started Guide: Provides a quick start reference to configuring and using the ESB.
JBoss ESB 4.2 Milestone Release 1 Programmers Guide: How to use JBossESB.
JBoss ESB 4.2 Milestone Release 1 Administration Guide: Information on how to manage the ESB.
JBoss ESB 4.2 Milestone Release 1 Services Guides: Various documents related to the services available with the ESB.
Questions or comments about JBoss ESB 4.2 Milestone Release 1 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.
This is a Milestone release for the next GA release of JBossESB. As such it contains a number of enhancements:
The deployment of JBossESB has been simplified through the use of the JBoss Microkernel. This gives greater flexibility and support for services and configuration.
JBoss Messaging 1.2.0GA is now the default JMS implementation. This has significant performance and reliability benefits over the other supported JMS implementations.
We now support jBPM integration. Please consult the Programmers Guide for more information.
A number of other examples have been added to show the individual capabilities within JBossESB more clearly.
A new configuration editor has been donated to the project.
We now have support for Groovy within the Action framework.
The following issues in the RC have been fixed in the GA:
[JBESB-382] - XML Marshaling/Unmarshling code uses the namespace prefix for performing namespace checking.
[JBESB-383] - XML Marshaling/Unmarshling code performs no normalisation on name values used to create XML/DOM element nodes.
[JBESB-388] - Querying for tModels causes NAMESPACE_ERR, null results and failure
[JBESB-389] - Transformation Console should support 1024 x 768
[JBESB-404] - No copyright statements in Quickstart files
[JBESB-406] - Race condition for threaded managed lifecycles
[JBESB-407] - In the Admin Console, replace the horrible home made lists with proper lists.
[JBESB-409] - Embeddded (local) Juddi
[JBESB-441] - Broken link on labs page
[JBESB-444] - Quick Starts didn't compile on Trunk
[JBESB-450] - Connection (Thread) leak in NotifyTopics and NotifyQueues
[JBESB-458] - FileGatewayListener cannot cope with zero length copy file
[JBESB-460] - Pool/Cache JMS connections
[JBESB-461] - Close connections to JNDI Context
[JBESB-466] - Incorrect classloading using Class.forName
[JBESB-475] - SmooksTransformer can no longer maintain a static ref to a StandaloneSmooks instance
[JBESB-477] - success and exception properties are no longer picked up for actions
[JBESB-478] - Redeploying the groovy quickstart loop problem
[JBESB-480] - FTP temp file down load fails.
[JBESB-481] - Select for update fails since you can't use BigIntegers in the PreparedStatement
The following issues are known and within JIRA:
The current release of JBoss Messaging (1.2.0GA) has a memory leak that causes problems for applications. Although this has been fixed, an official update to JBoss Messaging was not available at the time of the JBossESB release. As such we have shipped with modified messaging jars to fix this problem. We will move to the official jars when they are available. (http://jira.jboss.com/jira/browse/JBMESSAGING-920).
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.
In some circumstances getTemporaryReplyTo can generate an EPR that will be functionally identical to the original To EPR. If the client and service share the same transport mechanism (e.g., JMS queue) then it's possible that replies to the client may be lost because they get picked up by the service again. This will be fixed in the next release.
a config is updated with the server running, it goes into an
infinite loop with the following error:
18:32:43,465 ERROR [MessageAwareListener] Courier Exception org.jboss.soa.esb.couriers.CourierException: No courier defined for pick ups at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCo urierImpl.java:184)