JBoss Enterprise SOA Platform 5

5.3.1 Release Notes

Changes in this Release

Legal Notice

Copyright © 2013 Red Hat, Inc..
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.

Abstract

These notes document the changes found in this release of the JBoss Enterprise SOA Platform and the associated Enterprise Data Services product.
The JBoss Enterprise SOA Platform is a certified, tested, and supported environment for developing Enterprise Application Integration and SOA solutions.
For the latest version of these release notes please refer to the online copy available at http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/.

1. Overview

JBoss Enterprise SOA Platform is a certified, tested, and supported platform for developing Enterprise Application Integration and Service Oriented Architecture solutions.
It integrates a number of stable and scalable open source frameworks and solutions including Hibernate, Seam, JBoss Transactions, JBoss Clustering, the JBoss Application Server, and JBoss Enterprise Service Bus (ESB) to provide an infrastructure for enterprise SOA applications.
These community developed and enterprise certified and supported products have been combined and tested to provide a solid, robust, and scalable platform. Powered by legendary JBoss innovation and backed by Red Hat engineering and quality assurance, JBoss Enterprise SOA Platform is the platform of choice for a new generation of enterprise applications.

1.1. Frequently Asked Questions

1.1.1. Frequently Asked Questions

Q: Where is the documentation?
Q: Where are the installation instructions?
Q: Which operating systems, Java Virtual Machines and database servers are supported?
Q: Why isn't the included Hypersonic database supported?
Q: What components are included in this product?
Q: What is a Technology Preview?
Q: Where can I find out more details about my support entitlements?
Q: Where do I go to obtain the source code?
Q: Where do I go to report errors in the documentation?
Q: What is JBoss Enterprise Data Services Platform?
Q:
Where is the documentation?
A:
You can find the JBoss Enterprise SOA Platform documentation at https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_SOA_Platform/.
You can also find many articles about specific usecases at the Red Hat Customer Portal Knowledge Base: https://access.redhat.com/kb/knowledgebase/en.
Javadoc packages are available for download with the software at the Red Hat Customer Portal: https://access.redhat.com/jbossnetwork.

Note

Red Hat recommends reading the Getting Started Guide first as it contains instructions for installing and configuring the product.
Q:
Where are the installation instructions?
A:
Complete installation instructions for the JBoss Enterprise SOA Platform can be found in the Installation and Configuration Guide at https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_SOA_Platform/.
Q:
Which operating systems, Java Virtual Machines and database servers are supported?
A:
For a complete list of the supported operating systems, Java Virtual Machines (JVMs) and database servers on which you can run the JBoss Enterprise SOA Platform, refer to http://www.jboss.com/products/platforms/soa/supportedconfigurations/.
Q:
Why isn't the included Hypersonic database supported?
A:
The default configuration includes the embedded Hypersonic database. This configuration is included only for evaluation and demonstration purposes. It is not supported in a production environment.
You can read about this at https://access.redhat.com/kb/docs/DOC-41794.
The product now comes with H2, an in-memory reference database.
Q:
What components are included in this product?
A:
The list of components can be found here: http://www.jboss.com/products/platforms/soa/components/
Q:
What is a Technology Preview?
A:
Technology Preview features are not supported, may not be functionally complete, and are not intended for production use. These features are included to provide customers with early access to upcoming product innovations, enabling them to test functionality and provide feedback during the development process.
Red Hat JBoss support will provide commercially reasonable efforts to resolve any reported issues that customers experience when using these features.
Q:
Where can I find out more details about my support entitlements?
A:
Details of support policies can be found at the following URLs:
Q:
Where do I go to obtain the source code?
A:
The source code for this and earlier releases can be downloaded from the Red Hat Customer Portal at https://access.redhat.com/jbossnetwork/.
Q:
Where do I go to report errors in the documentation?
A:
Click on the "Report a bug" link under the topic in question. This will take you to Bugzilla and you can then fill out the details of the problem.
Q:
What is JBoss Enterprise Data Services Platform?
A:
JBoss Enterprise Data Services Platform is a new product that extends the JBoss Enterprise SOA Platform to provides services for data virtualization, federation and integration.
JBoss Enterprise Data Services Platform includes the following features:
  • Open source Data Virtualization engine based on the Teiid community project.
  • Data Services tooling is Integrated with JBoss Developer Studio v4 (Eclipse 3.6).
  • Data caching and staging enhancements.
  • Metadata repository based on Modeshape community project.
  • Management through admin-console. Management and Monitoring through JBoss Operations Network.
  • Updated data source support.
You can find out more about JBoss Enterprise Data Services Platform at https://www.jboss.com/products/platforms/dataservices/.

1.2. Resolved Issues

1.2.1. Resolved Issues

The following issues have been resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#780334 - Camel Gateway - loading of type converters doesn't work when esb package is deployed after long time of server idling
There is an issue with VFS caching and the deployment of non-core Camel components where the server has been running for more than thirty minutes. After the cache lifetime expires (30 minutes), if you deploy a non-core Camel component, an error is thrown. To work around this, deploy your application before starting the server or before this 30 minute limit, or raise the boss.vfs.cache.TimedPolicyCaching.lifetime property to a higher value. (No issue is present if you deploy a non-core Camel component before booting the server, or before the cache lifetime expires.)
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#821672 - New Quickstart: Camel Gateway esbschedule feature
A camel_esbschedule quickstart has been added to demonstrate the scheduling feature of CamelGateway.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#847767 - soa-p-5.3.0.GA-jbpm5 is not working.
The jBPM5 installation instructions (README.TXT) did not explain how to validate the installation of jBPM5. Users would not know if jBPM5 was installed correctly. The business-central URL is now mentioned in the installation instructions as a way of validating the installation. A link has also been added to the jBPM5 console to aid users who have installed the jBPM5 integration and the BRMS-P deployable. Users will now be able to validate their installation.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#861446 - Support "pass though" SQL commands to sources
Previously, there was no easy mechanism to allow a source specific query to be submitted to the runtime engine. Users needed to resort to user defined functions which can be unnecessarily complex. Source specific queries (or "native queries") can now be set in Teiid Designer. The runtime engine will then use this native query as an inline view instead of the respective table name within a FROM clause.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#862306 - Update jbpm.esb/jbpm-ds.xml configuration for MSSQL databases.
Issues arose from using jBPM with MS SQL Server 2005. When using these together, jBPM would experience deadlocks. This has been addressed through a revision of the mssql-ds.xml file. As a result, these deadlocks no longer occur.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#866339 - Uncommenting GenericPipelineInterceptors in jbossesb-properties.xml causes NullPointerException at startup
When using the JBoss ESB, a NullPointerException would occur at start-up in certain instances. This happened when a user uncommented GenericPipelineInterceptors in the jbossesb-properties.xml file. This has since been resolved. As such, this exception no longer occurs.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#866926 - Create index for the foreign key constraint on the JBPM_TASKINSTANCE.PROCINST_ column
Users have been experiencing deadlocks in JBPM due to a missing index. Deadlocks are now avoided with the addition of a new index according to the following: # the foreign key constraint (already present in jBPM ddl script): alter table JBPM_TASKINSTANCE add constraint FK_TSKINS_PRCINS foreign key (PROCINST_) references JBPM_PROCESSINSTANCE; # new index to add to the schema: create index IDX_TASKINST_PRCINS on JBPM_TASKINSTANCE (PROCINST_);
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#867066 - Ship javadocs for jbossesb-jbpm5.jar
The Javadocs were not included for the jBPM5 integration. Developers did not have the Javadoc to refer to for development purposes. The Javadocs are now included so developers have them available for reference.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#868874 - The "rewrite-endpoint-url" property of SOAPProcessor doesn't work for HTTP Gateway
Users experienced problems when specifying an endpoint URL while using the SOAPProcessor with HTTP Gateway. After setting the rewrite-endpoint-url to "false", the URL would persistently be overwritten and replaced with the original JBoss ESB URL. This was due to the Publisher not initialising with the Gateway. This has been resolved in the current release.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#875751 - Support Digital Signatures (jUDDI enhancement)
The upgrade to jUDDI 3.1.4 adds additional tables in order to support digital signatures. The files: add-juddi-tables.*.txt provided in the distribution contain the SQL commands that will create the additional tables when upgrading from SOA-P 5.3.0 to SOA-P 5.3.1.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#876274 SyncServiceInvoker does not reset ReplyTo and FaultTo EPR when deliverSync is succesful
SyncServiceInvoker sets the ReplyTo and FaultTo headers of the Call to null and they remain as null unless an Exception is thrown, in which case they will be set back to their original values. Now the ReplyTo and FaultTo headers also retain their original values when the process method succeeds, as expected.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#880065 - IllegalArgumentException in jBPM Console Task Variables pagination
When a task had more than 10 variables and you viewed task variables in jBPM Console, the view didn't limit results to 10 rows. When the "Next" link was selected, it threw an IllegalArgumentException. Results are now displayed as expected and no IllegalArgumentException is encountered.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#880811Colons need to be escaped
The modifySQL method in ODBCServerRemoteImpl handled '::' in queries incorrectly, resulting in unexpected results. Users have had to escape each of the colons to achieve the desired behavior. The modifySQL has been modified to identify occurrences of '::' correctly, so there is no longer a need to escape the colons in queries to achieve the expected behavior.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#880892 - Changes to jUDDI initialisation code to allow use of spaces within directories
Users were experiencing difficulties upon using jUDDI with certain directories. Directories containing spaces in their names were not loading properly. This has been patched for the current release. Directories with spaced names now appear as expected.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#881861Http Provider returns 200 http response code for Soap Fault
In previous releases, an incorrect error would be displayed when using the JBoss ESB pipeline with SOAPProcessor actions to call a Web Service. If the wrapped web service returned a soap fault and HTTP response code 500, the HTTP Provider Gateway returned a response code 200 instead of the expected 500 response. This has been patched in the current release. Users will see the correct code 500.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#881924org.jboss.internal.soa.esb.message.format.xml.marshal.SerializedMarshalUnmarshalPlugin.unmarshal throws ClassNotFoundException when WSDL is not available to SoapUI
The soapui-1.7.1.jar is not included in the jboss-as/server/configuration/deployers/esb.deployer/lib/ directory resulting in a ClassNotFoundException. To workaround this issue, the user can add the JAR file to this directory manually. Manual instructions: Copy the soapui-1.7.1.jar from jboss-as/server/configuration/deploy/soapui-client.sar/lib to jboss-as/server/configuration/deployers/esb.deployer/lib directory. Note: The platform with this modification has been tested only for the purpose of verifying issue BZ-881924.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#882845 - Upgrade Camel to 2.10.2
Camel has been upgraded to version 2.10.2 for the JBoss ESB. This update fixes several of the bugs associated with older versions of Camel.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#885095 - NPE with proc relational query
FrameUtil.isProcedure does not check that projectNode != null. This means that a proc relational query using a table function or other source without an access node will fail with a NullPointerExcpetion. FrameUtil.isProcedure now checks that projectNode != null before proceeding and no such exception is experienced.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#895304 - Cannot execute Two-Phase Commit using Multi-Source Model Dynamic VDB
Users are experiencing problems when updating on multi-source models. If you are using multi-source models, performing updates, and using the default PROP_TXN_AUTO_WRAP of DETECT, then try to explicitly set the transaction mode by using of the following methods: * local (START TRANSACTION or setAutoCommit(false) * global/XA * set autoCommitTxn=ON on the URL
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.
BZ#896640 - JBpmObjectMapper doesn't handle missing variables properly
If one of the jBPM variables was missing when mapping from jBPM to ESB an exception was thrown. Now if a jBPM variable is missing (has a null value), the user will receive a log warning, not an exception.
This issue was resolved in JBoss Enterprise SOA Platform 5.3.1.

1.3. Known Issues

1.3.1. Known Issues

The following issues are known to exist in JBoss Enterprise SOA Platform 5.3.1 and will be fixed in a subsequent release.
BZ#781067 - New Behavior for consideration-- on HTTP 500, have SOAPClient throw an Exception that is palatable downstream
When SOAPClient is used and an HTTP 500 Error is encountered, SOA-P throws an Exception containing the HTTP 500 stack trace which is not handled by ActionProcessingPipeline, resulting in an uninformative message.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#850891 - AbstractBpm5Action is registering handlers too freely
There is an issue with the way in which AbstractBpm5Action is registering handlers when processes start. When a user closes a task via the console, a race condition is causing an exception to occur.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#874196 - RollupClone - New Behavior for consideration-- on HTTP 500, have SOAPClient throw an Exception that is palatable downstream
When SOAPClient is used and an HTTP 500 Error is encountered, SOA-P throws an Exception containing the HTTP 500 stack trace which is not handled by ActionProcessingPipeline, resulting in an uninformative message.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#874669 - Upgrade to juddi 3.1.4
It is desired that integration with jUDDI be upgraded for jUDDI version 3.1.4.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#876337 - Please fix FileUtils.move (Code enclosed)
FileUtil.renameTo(..) returns true even if it fails to rename the file. As a result, when a file that is locked by another process is picked up by the SOA platform, and the rename fails, an error is logged even though the file is processed successfully on the next attempt (when the lock is gone).
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#895624 - Please fix Drools in SOA-P so old rules will still run
Users were finding that rules that used to work now result in Exceptions. To fix, it is suggested that the source code should be updated to use a new class instance directly, rather than via a declared constant.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#902888 - Please allow user to specify defaults in esbToBpmVars
Our product no longer allows the use of default values in the mapping from ESB to jBPM variables (esbToBpmVars).
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#819572 - jBPM ant deploy task returns 0 rc if pingServer() fails
If a jBPM3 process is deployed using the ant task and the server cannot be reached, a value of "0" will be returned instead of an error message. If you are trying to connect to a server and receive this value, check to make sure that the server is available before redeploying.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#847290 - http-gateway returns invalid empty WSDL document.
The HTTP gateway would return an invalid, empty WSDL document in certain circumstances. It was invalid because it was not in the correct namespace. Furthermore, the http-gateway should not return a WSDL document by default since it may be used with more than just SOAP.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#881131 - Creating a new jBPM3 project does not open the jBPM perspective
When creating a new jBPM3 project, JBDS should provide the option to go into the jBPM jPDL perspective to be consistent with the behavior when creating other types of projects. Currently, when creating a new jBPM3 project, all that happens is that the project is created.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#893362 - EBWS enabled service cannot be deployed when space is present in server directory name (NPE)
If the JBoss Enterprise SOA Platform is installed into a directory which has a space in its name then the ESB archive cannot be deployed as a null-pointer exception is thrown. To work around this issue, add "-Dorg.jboss.net.protocol.file.useURI=false" to your start-up script.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.
BZ#902812 - Output of JNDI View MBean, invoked through jmx-console has bad html markup
The output of JNDI View MBean, invoked through jmx-console, renders incorrectly. This is because, in the HTML source code, HTMNL tags are encoded with < and >, so they do not displayed properly in browsers.
This behavior persists in JBoss Enterprise SOA Platform 5.3.1.

1.4. New Features

The following are available in this release:

1.4.1. New Features

Java
Java 7 is now supported.

A. Revision History

Revision History
Revision 5.3.1-1.4002013-10-31Rüdiger Landmann
Rebuild with publican 4.0.0
Revision 5.3.1-1Mon Feb 18 2013Suzanne Dorfield, David Le Sage, Ben Long
Release notes for JBoss Enterprise SOA Platform 5.3.1