Version 4.4.1
Copyright © 2011-2013 Red Hat, Inc. and/or its affiliates.
Updated: 13 Jun 2013
Table of Contents
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-08-15 |
| Fuse Services Framework | 2.4.3-fuse-04-15 |
| Fuse Mediation Router | 2.8.0-fuse-07-15 |
| Fuse Message Broker | 5.5.1-fuse-08-15 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-08-15 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-06-11 |
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-07-11 |
| Fuse Services Framework | 2.4.3-fuse-03-02 |
| Fuse Mediation Router | 2.8.0-fuse-06-11 |
| Fuse Message Broker | 5.5.1-fuse-07-11 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-07-11 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-06-11 |
This is a note if you are building Fuse ESB from source using the offline repository. You can ignore otherwise.
Several Eclipse artifacts use version ranges (ex.
org/eclipse/core/resources/3.3.0-v20070604/resources-3.3.0-v20070604.pom
depends on org.eclipse.core:expressions:[3.1.0,4.0.0)). In offline mode,
Maven cannot download metadata from a remote repository to determine what versions are
available because it requires local metadata. In the case of the Eclipse libraries, this
metadata is saved under the "nexus" host name. To get Maven to pick up this metadata, you
need the following settings.xml profile with a "nexus" repositories
added:
<settings>
<profiles>
<profile>
<id>offlinerepo</id>
<repositories>
<repository>
<id>nexus</id>
<url>file:///path/to/offline/repo</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>nexus</id>
<url>file:///x1/offlinerepos/repo</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>offlinerepo</activeProfile>
</activeProfiles>
</settings>You only need this when using an offline repository locally to build from source. For example, if you build like this:
mvn clean install -Dmaven.repo.local=/path/to/offline/repo --offline
If you import the offline repository into a repository manager like Nexus or Artifactory on your local network then you will not encounter this issue.
The following bug was fixed in this release:
ESB-1722 - A
ResourceManager that is registered with
activemq-broker.xml is configured incorrectly.
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-06-03 |
| Fuse Services Framework | 2.4.3-fuse-03-02 |
| Fuse Mediation Router | 2.8.0-fuse-05-03 |
| Fuse Message Broker | 5.5.1-fuse-06-03 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-04-06 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-05-03 |
This is a note if you are building Fuse ESB from source using the offline repository. You can ignore otherwise.
Several Eclipse artifacts use version ranges (ex.
org/eclipse/core/resources/3.3.0-v20070604/resources-3.3.0-v20070604.pom
depends on org.eclipse.core:expressions:[3.1.0,4.0.0)). In offline mode,
Maven cannot download metadata from a remote repository to determine what versions are
available because it requires local metadata. In the case of the Eclipse libraries, this
metadata is saved under the "nexus" host name. To get Maven to pick up this metadata, you
need the following settings.xml profile with a "nexus" repositories
added:
<settings>
<profiles>
<profile>
<id>offlinerepo</id>
<repositories>
<repository>
<id>nexus</id>
<url>file:///path/to/offline/repo</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>nexus</id>
<url>file:///x1/offlinerepos/repo</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>offlinerepo</activeProfile>
</activeProfiles>
</settings>You only need this when using an offline repository locally to build from source. For example, if you build like this:
mvn clean install -Dmaven.repo.local=/path/to/offline/repo --offline
If you import the offline repository into a repository manager like Nexus or Artifactory on your local network then you will not encounter this issue.
The following bugs were fixed in this release:
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-04-06 |
| Fuse Services Framework | 2.4.3-fuse-01-02 |
| Fuse Mediation Router | 2.8.0-fuse-03-06 |
| Fuse Message Broker | 5.5.1-fuse-03-06 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-04-06 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-03-06 |
This is a note if you are building Fuse ESB from source using the offline repository. You can ignore otherwise.
Several Eclipse artifacts use version ranges (ex.
org/eclipse/core/resources/3.3.0-v20070604/resources-3.3.0-v20070604.pom
depends on org.eclipse.core:expressions:[3.1.0,4.0.0)). In offline mode,
Maven cannot download metadata from a remote repository to determine what versions are
available because it requires local metadata. In the case of the Eclipse libraries, this
metadata is saved under the "nexus" host name. To get Maven to pick up this metadata, you
need the following settings.xml profile with a "nexus" repositories
added:
<settings>
<profiles>
<profile>
<id>offlinerepo</id>
<repositories>
<repository>
<id>nexus</id>
<url>file:///path/to/offline/repo</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>nexus</id>
<url>file:///x1/offlinerepos/repo</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>offlinerepo</activeProfile>
</activeProfiles>
</settings>You only need this when using an offline repository locally to build from source. For example, if you build like this:
mvn clean install -Dmaven.repo.local=/path/to/offline/repo --offline
If you import the offline repository into a repository manager like Nexus or Artifactory on your local network then you will not encounter this issue.
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-03-05 |
| Fuse Services Framework | 2.4.3-fuse-01-02 |
| Fuse Mediation Router | 2.8.0-fuse-02-05 |
| Fuse Message Broker | 5.5.1-fuse-02-05 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-03-05 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-02-05 |
This release has the following known issues:
There is a problem with the ActiveMQJmsRequestorPool used in the
jbi-cluster feature. In this release the
GenericJmsRequestorPool is used instead. This issue will be fixed
in a future release and is logged in ESB-1646.
You may see the following error on subsequent starts of the ESB:
log4j:WARN No appenders could be found for logger (org.apache.felix.configadmin). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
This is fixed in the next major release and is being costed for the next service pack release. The issue is logged as ESB-1647.
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-03-02 |
| Fuse Services Framework | 2.4.3-fuse-01-02 |
| Fuse Mediation Router | 2.8.0-fuse-02-02 |
| Fuse Message Broker | 5.5.1-fuse-02-02 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-02-13 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-01-13 |
The following bugs were fixed in this release:
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-02-13 |
| Fuse Services Framework | 2.4.3-fuse-00-13 |
| Fuse Mediation Router | 2.8.0-fuse-01-13 |
| Fuse Message Broker | 5.5.1-fuse-01-13 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-02-13 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-01-13 |
This is a note if you are building Fuse ESB from source using the offline repository. You can ignore otherwise.
Several Eclipse artifacts use version ranges (ex.
org/eclipse/core/resources/3.3.0-v20070604/resources-3.3.0-v20070604.pom
depends on org.eclipse.core:expressions:[3.1.0,4.0.0)). In offline mode,
Maven cannot download metadata from a remote repository to determine what versions are
available because it requires local metadata. In the case of the Eclipse libraries, this
metadata is saved under the "nexus" host name. To get Maven to pick up this metadata, you
need the following settings.xml profile with a "nexus" repositories
added:
<settings>
<profiles>
<profile>
<id>offlinerepo</id>
<repositories>
<repository>
<id>nexus</id>
<url>file:///path/to/offline/repo</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>nexus</id>
<url>file:///x1/offlinerepos/repo</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>offlinerepo</activeProfile>
</activeProfiles>
</settings>You only need this when using an offline repository locally to build from source. For example, if you build like this:
mvn clean install -Dmaven.repo.local=/path/to/offline/repo --offline
If you import the offline repository into a repository manager like Nexus or Artifactory on your local network then you will not encounter this issue.
The following bugs were fixed in this release:
The following improvements were made in this release:
SMX4-988 - should add delay to camel timer of camel-nmr and camel-nmr-blueprint example so that the nmr endpoint get chance to create
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-02-06 |
| Fuse Services Framework | 2.4.3-fuse-00-06 |
| Fuse Mediation Router | 2.8.0-fuse-01-06 |
| Fuse Message Broker | 5.5.1-fuse-01-06 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-02-06 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-01-06 |
The following bugs were fixed in this release:
ESB-1571 - Some of the dependencies in Fuse ESB source are out-of-date with Apache Camel 2.8 dependencies and Apache CXF.
ESB-1576/SMX4-910 - Installing activemq-web-console feature creates an activemq.base directory in the ESB home directory.
ESB-1598/SMX4-924 - Fuse ESB should ship servlet api 2.5 but not servlet api 3.0.
ESB-1605 - The camel feature doesn' resolve on boot.
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-02-06 |
| Fuse Services Framework | 2.4.3-fuse-00-06 |
| Fuse Mediation Router | 2.8.0-fuse-01-06 |
| Fuse Message Broker | 5.5.1-fuse-01-06 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-02-06 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-01-06 |
The following bug was fixed in this release:
The following improvements were made in this relase:
ESB-1563 - use last version of Servicemix antlr bundle for jpa-hibernate feature
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-00-08 |
| Fuse Services Framework | 2.4.2-fuse-00-08 |
| Fuse Mediation Router | 2.8.0-fuse-00-08 |
| Fuse Message Broker | 5.5.1-fuse-00-08 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-00-08 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-00-08 |
When building the source for the ESB (either apache-servicemix-4.4.1-fuse-00-08-src.zip or apache-servicemix-4.4.1-fuse-00-08-src.tar.gz) you may get a failure building the "assembly" module only when overriding the Maven local repository directory. To override the Maven repository directory you would pass in -Dmaven.repo.local=/path/to/repo.
To overcome this error you can either: (1) use the default Maven repo location of $\{user.home\}/.m2/repository, or (2) change the default Maven repo location in the settings.xml file as follows:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<localRepository>/path/to/repo</localRepository>
...
</settings>The following improvements were made in this release:
The following tasks were completed for this release:
ESB-1545 - Fuse ESB - Removing JBI features, may cause issue with using ActiveMQ afterwards
This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-00-06 |
| Fuse Services Framework | 2.4.2-fuse-00-06 |
| Fuse Mediation Router | 2.8.0-fuse-00-06 |
| Fuse Message Broker | 5.5.1-fuse-00-06 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-00-06 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-00-06 |
The following bugs were fixed in this release:
ESB-1376/SMX4-801 - incorrect CXF dependency versions in features descriptor
ESB-1378/SMX4-768 - Missing "in/client"shell script from 4.3.1-fuse-00-00
ESB-1426/SMX4-784 - activemq:list/activemq:query/activemq:bstat command doesn' work
ESB-1444/SMX4-852 - Fuse ESB closes SSH connection and doesn' respond to subsequent connection if features:install fails to find one of the bundles listed.
ESB-1485/SMX4-867 - the endorsed xml-api jar can' correctly load org.apache.xpath.jaxp.XPathFactoryImpl class
ESB-1501/SMX4-873 - system bundle should export xerces and xalan package as we already endorse those jar
ESB-1507/SMX4-899 - java.lang.IllegalArgumentException: http://www.w3.org/2001/XMLSchema
ESB-1517 - commons-dbcp component doesn' allow dynamic imports, resulting in problem loading oracle jdbc driver
ESB-1530/SMX4-912 - 4.4.0 features file references different version of spring-dm than we what we ship
SMX4-771 - simple example use out-of-date DocumentFactory
SMX4-804 - ensure some bundle could be installed with OBR resolver
SMX4-810 - ODE 1.3.5 is not compatible with Karaf 2.2.x
SMX4-869 - Missing class reference in the log:display output
SMX4-897 - reuse woodstox feature but not list seperate bundle
SMX4-907 - BOM marker in camel-osgi Spring XML file not handled well on CI server
The following improvements were made in this release:
ESB-1220/SMX4-794 - Create a top-level parent pom that only contains dependencies/versions.
ESB-1424/SMX4-791 - Make allowCoreThreadTimeout name consistent across mbeans and properties
ESB-1429/SMX4-799 - Package the latest version of Xerces to resolve an issue with the packaged jaxp-ri implementation
ESB-1439/SMX4-805 - Ignore the sun saaj package from the org.osgi.framework.bootdelegation
ESB-1442/SMX4NMR-270 - Optimize uuid generator in ExchangeImpl.java
ESB-1443/SMX4-808 - Ignore the sun jaxb package from the org.osgi.framework.bootdelegation
ESB-1458/SMX4-825 - camel-nmr producer should support timeout
ESB-1531 - Auto generate NOTICE file from all libs
ESB-1532/SMX4-871 - README.txt file incomplete for "imple"example in regards to the wsn.xml file.
ESB-1533/SMX4-870 - Expected results in the readme in our camel osgi example are incorrect
ESB-1537/SMX4-895 - Add last version of Servicemix antlr bundle into the next release of Fuse ESB 4.4.x
SMX4-654 - Improve features.xml to leverage OBR improvements in Karaf
SMX4-722 - Update POMs to Maven3
SMX4-778 - Rework the smx4 build to have better dependency handling
SMX4-787 - Upgrade to ActiveMQ 5.5.0
SMX4-792 - Support run as subject for Camel NMR endpoint
SMX4-793 - Support run as subject for CXF NMR endpoint
SMX4-798 - Ensure OBR support is available before boot features are installed
SMX4-815 - upgrade to cxf 2.4.0
SMX4-882 - specify start-level as 50 for default installed jbi component features which ensure jbi component related bundle can get started before customer bundles when restart OSGi container
The following tasks were completed for this release:
SMX4-752 - Switch to use slf4j as logger (instead of commons-logging)
SMX4-785 - upgrade to cxf 2.3.3
SMX4-856 - Upgrade to Java Mail 1.4.4
SMX4-861 - upgrade to cxf 2.4.1
SMX4-881 - Upgrade to Groovy 1.8.0
SMX4-887 - Upgrade to Quartz 1.8.5
SMX4-902 - upgrade to cxf 2.4.2
SMX4-903 - upgrade to jetty 7.4.5.v20110725
SMX4-906 - upgrade xmlsec and opensaml bundle version