Release Notes - FUSE ESB - Version 3.4.0.6-fuse - July 29th, 2010

Bug

• ESB-1109 - namespace stripped from request
• ESB-1200 - Prefix mapping dropped leads to invalid xml
• ESB-1229 - HTTP Consumer Timeout doesn't work

Improvement

• ESB-1195 - Upgrade to log4j 1.2.16

Task

• ESB-1180 - MEP parameter gets appended to service/endpoint name

Known issues

• When starting the container, you get this warning when the servicemix-lwcontainer JBI component is being installed. The warning is harmless and should not have any implications at runtime.

  Unable to add File ../lib/servicemix-shared-2009.01.0.6-fuse-installer.zip
  to class path as it doesn't exist
  

Summary

This release packages the following Fuse dependencies.

Release Notes - FUSE ESB - Version 3.4.0.5-fuse - April 10th, 2010

Bug

• ESB-1035/SMXCOMP-681 - add xml-resolver dependency explicitly to ensure org/apache/xml/resolver/CatalogManager is available
• ESB-1076/SMXCOMP-618 - soap-provider strips off namespace from incoming response
• ESB-1080/SM-1918 - Migrate ESB-965 to the 3.4 branch
• ESB-1091/CXF-2618 - cxf-bc: secureSocketProtocol in TLSClientParams and TLSServerParams is not pushed into the SSLSocketFactory
• ESB-1122/SMXCOMP-706 - Merge cxf-bc interceptor chain management fix into 3.4.0.x branch
• ESB-1162/SMXCOMP-727 - ws-rm client can't invoke on a ws-rm enabled CXF BC web service
• ESB-1166 - Can't configure ws-rm service with a decoupled endpoint.
• ESB-1171/SMXCOMP-730 - cxfbc provider can't load schema files located in relative paths
• ESB-674/SMXCOMP-618 - servicemix-cxf-bc provider and org.apache.ws.security.WSSecurityException: The signature or decryption was invalid error
• ESB-809 - ScriptingComponentTest and CxfBcProviderConsumerTest failures with the ibm jdk
• ESB-816/SMXCOMP-613 - Tests failled while doing a components 2009.01.0.4-fuse release.
• ESB-819/SMXCOMP-616 - Schema validation with cxf-bc component is not working.
• ESB-826/SMXCOMP-617 - CXF-BCProvider and JbiOutWsdl1Interceptor generate classcast exception in case where JBI messageExchange have newline characters in xml (formatted xml).
• ESB-835/SM-1904 - Maven archetype "servicemix-osgi-camel-archetype" with camel 1.6 and 2.0 dependency is not available
• ESB-855 - cxf-ws-security example fails with the ibm jdk
• ESB-909/SMXCOMP-638 - NotSerializableException with JMSFlow when camel returns an exception.
• ESB-915/SMXCOMP-640 - smx-eip async AbstractSplitter throws UnsupportedOperationException when reportErrors="true".
• ESB-952 - HTTP Consumer Endpoint timeouts when there is no timeout
• ESB-955/CXF-2517 - Wiretap faultListener doesn't receive exception thrown by Java-first CXF SE service
• SM-1892 - Port property is not passed to any Servicemix Ant tasks in servicemix-ant-tasks.xml (install-component, etc)
• SM-1914 - ServiceMix fails to start when JAVA is installed under path containing spaces
• SM-1915 - Support more fine-grained authorization on JMX access
• SM-1924 - @{releases-repo-url} not filtered in smx-arch/smx-arch.bat
• SM-1925 - Add security check on remote broker when using JMSFlow/JCAFlow
• SM-1926 - Statistics Service throws NPE with DynamicEndpoints
• SM-1933 - Sample poms refer to people.apache.org instead of repository.apache.org for snapshot

Improvement

• ESB-1009 - Please update the Jetty version in the servicemix-http component to the latest stable version.
• ESB-1015/SM-1911 - Upgrade Derby to 10.5.3.0 in ServiceMix
• ESB-1104/SMXCOMP-702 - FUSE ESB New JMS Provider endpoint should allow per message setting of JMSPriority or JMSTimeToLive
• ESB-1111/SMXCOMP-703 - Servicemix CXF-BC component JbiJAASInterceptor should catch UndeclaredThrowableException
• ESB-1155 - Add property to smx 3.3 startup scripts to workaround xerces bug
• ESB-863 - avoid using hardcode version in caml-sa-itest
• SM-1899 - Upgrade to jenck 2.2
• SM-1922 - remove unnecessary kit_camel_example_pom.xml from camel example of kit
• SM-1929 - Upgrade SMX3 to use CXF 2.2.6
• SM-1937 - Incorrect logic in throttle method of DeliveryChannelImpl.java

New Feature

• SM-788 - start/stop/restart on SM

Task

• ESB-1023/SMXCOMP-676 - CxfBcRMSequenceTest.testInactivityTimeout failed intermittently especially on windows teamcity machine
• ESB-1034 - CxfBcAddressingTest.testExplicitMAPs failed on teamcity
• ESB-1097/SM-1930 - Upgrade geronimo jars to 2.1.3
• SM-1877 - update wss4j to 1.5.8
• SMX4-201 - Upgrade to woodstox 4.x as it comes natively as an osgi bundle

Summary

This release packages the following Fuse dependencies.

Release Notes - FUSE ESB - Version 3.4.0.4-fuse - July 31st, 2009

Bug:

• ESB-769/SM-1873 - GenerateServiceAssemblyMojo doesn't include any files created by a build such as resources
• SM-1865 Add a sample showing SMX JMX client usage
• SM-1878 refactor client.html used in cxf-wsdl-first

Summary

This release packages the following Fuse dependencies.

Release Notes - FUSE ESB - Version 3.4.0.3-fuse - July 08th, 2009

Summary

This release packages the following Fuse dependencies.

Because ESB 3.4.0.3-fuse shares components with FUSE ESB 4.1 the components have been moved to a different source package.

FUSE ESB 3.4.0.3-fuse now shares JBI components with FUSE ESB 4.1. Fixes that are part of Shared JBI components can be found here. Here are a few additional fixes that are available in 3.4.0.3-fuse:

Bug

• ESB-560 SM-1776 - in-out cxf-bc async jms consumer with cxf-se provider loses messages under load with no errors reported
• ESB-647 SMXCOMP-18 - Camel component unuseable when servicemix is configured to use JMSFlow
• ESB-694 - Build of 3.4.0.1 on AIX 5.3 JDK6, 64-bit fails
• ESB-740 SM-1867 - The FUSE 3.4.0.2 seems to have an inconsistent version of the spring-aop.jar

Improvement

• ESB-755 SM-1872 - FUSE ESB CXF-BC and CXF-SE should allow separate configuration for non-default busCfg at component level
• SM-1574 - Allow forced shutdown of the container by cancelling pending sendSync exchanges

Task

• ESB-566 SMXCOMP-28 - Ensure that SF-170 is integrated into FUSE ESB 3.3.x CXF BC
• ESB-716 - Add unit test for the new 'forceShutdown' option introduced in ESB-310

Release Notes - FUSE ESB - Version 3.4.0.2-fuse - May 08th, 2009

Summary

This release packages the following Fuse dependencies.

Because ESB 3.4.0.2-fuse shares components with FUSE ESB 4.1 the components have been moved to a different source package.

FUSE ESB 3.4.0.2-fuse now shares JBI components with FUSE ESB 4.1. Fixes that are part of Shared JBI components can be found here. Here are a few additional fixes that are available in 3.4.0.2-fuse:

Bug

• SMXCOMP-176 - Support JarUrlConnection with regexp in the SU <classpath/>
• SM-1749 - Incorrect Logger name creation in ComponentContextImpl
• https://issues.apache.org/activemq/browse/SM-1810
• SM-1817 - Publish components schema files as part of the distribution in a schemas/ directory
• SM-1821 - ESB hangs on exit when destroyApplicationContextOnShutdown is set to true and the broker's persistent storage fails
• SM-1822 - Add JMS connection credentials to JCAFlow
• SM-1824 - BUG in JDK6 ReentrantReadWriteLock can cause SMX hang when redeploy SA
• SM-1845 - keystore.jks should be filtered during distribution package
• SM-1853 - ClassCast exception in ClassLoaderXmlPreprocessor

• ESB-73 - Response stream not available (already closed) in InOut MEP when using Camel route and http-provider
• ESB-424 - Camel component should allow JbiBinding settings on an SU basis
• ESB-570 - ESB container hangs when redeploying multiple SAs and concurrently processing messages
• ESB-571 - Hotdeployment of CXF SA with changed keystores fails
• ESB-575 - CXF BC Consumer addes xmlns for each element when using prefixes
• ESB-577 - Refactor JmsProviderEndpoint to not use reflection to call protected method on Spring JmsTemplate class
• ESB-580 - Change "Content-Type" String property in DefaultProviderMarshaler
• http://fusesource.com/issues/browse/ESB-582
• ESB-583 - smx-file async FilePollerEndpoint needs a throttling mechanism to avoid creating excessive numbers of open exchanges and overloading the nmr
• ESB-586 - ActiveMQ configuration in ESB 3.4 uses old namespace
• ESB-595 - ESB hangs on exit when destroyApplicationContextOnShutdown is set to true and the broker's persistent storage fails
• ESB-604 - jms archetypes generate extra http:// for xmlns:xsi namespace.
• ESB-606 - Unable to deploy a second secure service using WS-Security on a port already in use for another secure
• ESB-620 - Problem with Camel SU archetype
• ESB-621 - Deadlock introduced into straight through flow in FUSE ESB versions after 3.3.1.4
• ESB-634 - Asynchronous messages not delivered by camel route back to smx endpoints.
• ESB-652 - CXF Provider binding component relies on garbage collection to clean up proxies/connections
• ESB-655 - ConcurrentModificationExceptions under heavy load in CXF BC

Improvement

• ESB-601 - Port bridge sample to use camel instead of eip component

New Feature

Release Notes - FUSE ESB - Version 3.4.0.1-fuse - February 10, 2009

Summary

This release packages the following Fuse dependencies.

Because ESB 3.4.0.0-fuse shares components with FUSE ESB 4.0 the components have been moved to a different source package.

FUSE ESB 3.4.0.0-fuse now shares JBI components with FUSE ESB 4.0. Fixes that are part of Shared JBI components can be found here.
Here are a few additional fixes that are available in 3.4.0.0-fuse:

Bug

SM-1592cxf-bc consumer should allow async sending of message exchanges to the NMR.
SM-1742Removal of HttpManagedServlet is causing servicemix-web sample to fail. This will also be addressed in the next patch.
[SM-1757] TransformComponentSupport does not handle errors nor does it support robust-in-only MEPs.
[SM-1761] AutoDeploymentService stops working after x deployments.
[SM-1791] org.apache.servicemix.jbi.framework.InstallerMBeanImpl is missing bootstrap.init() call on uninstall phase which is required as per JBI specs.

Improvement

New Feature

Release Notes - FUSE ESB - Version 3.4.0.0-fuse - December 24, 2008

Summary

This release packages the following Fuse dependencies.

This release contains all fixes from FUSE ESB 3.3.1.12-fuse release. Also, FUSE ESB 3.4.0.0-fuse now shares JBI components with FUSE ESB 4.0 - fixes can be found here. Here are a few additional fixes that are available in 3.4.0.0-fuse:

Bug

[ESB-390] During FUSE-ESB Startup and potentially during multi-SA deployment, ensure all SA endpoints are "registered" before starting any endpoints.
[ESB-250] javax.jms.JMSException: java.util.ConcurrentModificationException in JMS consumer endpoint (Fuse ESB) when doing high load test.
[ESB-521][SM-1744] CXF Binding Component throws null pointer exception when using jax-ws-catalog.

Improvement

[ESB-282] Upgrade Drools engine in FUSE ESB to version 4.0.7.
[SM-1709] unify third party libs used across servicemix projects.

New Feature

Known Issues:

SM-1592: "cxf-bc consumer should allow async sending of message exchanges to the NMR" is not part of this release because it depends on some latest changes related to jetty ContinuationWrapper in Fuse Services Framework which are not available in FUSE SF 2.1.3.1-fuse. This will be addressed in the next patch.
SM-1742: Removal of HttpManagedServlet is causing servicemix-web sample to fail. This will also be addressed in the next patch.