Home / / Fixed Bugs and Changes in Vortex Gateway

Fixed Bugs and Changes in Vortex Gateway

635 views Less than a minute

New releases of Vortex Gateway are made available on a regular basis. This page lists all the bug fixes and changes in the different versions. See this article for Known Issues in Vortex Gateway.

Release History

VersionDateDescription
2.3.142804Vortex V2.4
2.3.042635Vortex V2.3.0
2.2.242482Vortex V2.2.0
2.2.142417Vortex V2.1.0
2.2.042333Vortex V2.0.0
2.1.242193Maintenance release
2.1.142072Vortex V1.2.0
2.1.041918Vortex V1.1.0
2.0.141852Vortex V1.0.1
2.0.041831Vortex V1.0.0
1.3.141530Add readMode for camel-ospl component
1.3.041361Now based on the same DDSI implementation than OpenSplice Mobile
1.2.041123Add dynamic QoS for camel-ospl and fragmentation for camel-ddsi
1.1.141012Bug fix
1.1.041012New camel-ddsi component
1.0.440912Code obfuscation and some bug fixes
1.0.340863Provide support for 64 bit Windows and Solaris
1.0.240842Changed product name to OpenSplice Gateway
1.0.140828Minor corrections to 1.0.0
1.0.040821First release

Version 2.3.1

Report ID.Description
BB-298Vortex Gateway is now based on Vortex Café 2.3.1. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).
BB-299Fixed "%1 is not a valid Win32 application" error occuring on Windows with Maven 3.3.9, when installing Vortex Gateway with command "mvn -f VortexGateway-installation.pom".

Version 2.3.0

Report ID.Description
BB-287Vortex Gateway is now based on Vortex Café 2.3.0. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).
BB-288Vortex Café now supports Java 7 and 8. It's tested with both Oracle Java 8 and OpenJDK 8. Note that Java 6 is no longer supported.
BB-289The Maven build system for examples have been updated to build with Apache Maven 3.3.x. Apache Maven 3.3.9 is now delivered with Vortex Gateway, in place of Apache Maven 3.0.5.

Version 2.2.2

Report ID.Description
BB-276Vortex Gateway is now based on Vortex Café 2.2.2. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).
BB-277Fix tables rendering in PDF User Guide.

Version 2.2.1

Report ID.Description
BB-251Update all the "shapes-*" examples to work with Vortex Café 2.2.1 iShapes example, but also with OpenSplice and Lite iShapes demos.
 BB-268Vortex Gateway is now based on Vortex Café 2.2.1. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).
BB-271Fix the shapes-java example when using the DynamicPollEnricher.

Version 2.2.0

Report ID.Description
 BB-248Vortex Gateway is now based on Vortex Café 2.2.0. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).

Version 2.1.2

Report ID.Description
BB-207Add a 'ignoreLocalPublishers' option (boolean; true by default) to the camel-ospl component. When true, this option avoids loop in case of bridge pattern (1 route to DDS + 1 route from DDS).
BB-238Add options to the camel-ddsi component to set QoS at topic-level (see user guide for the full list of options).
BB-240Fix opensplice-idl-plugin to accept files with ".IDL" (uppercase) as extension.

Version 2.1.1

Report ID.Description
BB-215Add an etc/ directory in Vortex Gateway installation directory. User can copy its license file within.
BB-222Change user guide document to be available in both HTML and PDF formats. Remove installation guide, as now part of the Vortex installer.
BB-229Vortex Gateway is now based on Vortex Café 2.1.1. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).
OSPL-5470Fix warning displayed by idl2j, the camel-ospl component and the camel-ddsi component: "Java HotSpot(TM) Server VM warning: You have loaded library /tmp/librlm913-5386386880551815362.so which might have disabled stack guard".
BB-236Fix issue with OpenSplice 6.5.0 (and upper versions) leading a camel-ospl endpoint to not receive DDS samples under certain circumstances. NOTE that this means that Gateway version prior to 2.1.1 won't work correctly with OpenSplice 6.5.0 and following versions.

Version 2.1.0

Report ID.Description
BB-212Update RLM licensing library to no more require environment variables. As a consequence the "release.com" file is no more generated and doesn't need to be sourced any more. Please see the Vortex Installation Guide for the installation of your license file.
BB-211Vortex Web is now based on Vortex Café 2.1.0. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).
BB-213Update the LICENSE terms (see LICENSE.html).

Version 2.0.1

Report ID.Description
BB-204Vortex Gateway's camel-ddsi is now based on Vortex Café 2.0.1. The camel-ddsi component benefits some of its fixes and improvements (see Café's changes).

Version 2.0.0

Report ID.Description
BB-157Changed product name to "Vortex Gateway" This implies following changes: 1- In all pom.xml file Maven groupId change org.opensplice.gateway to com.prismtech.gateway 2- In Java source code : change org.opensplice.gateway to com.prismtech.gateway .
BB-141Changed default Camel version to 2.10.0.redhat-60060 .
 BB-158The camel-ddsi component uses the same DDSI implementation than Vortex Café v2.0.0 .
BB-160The logging have been improved. The logs are prefixed with "gateway.ospl" for the camel-ospl component, and with "gateway.ddsi" for the camel-ddsi component.
BB-187Added descriptions in User Guide of the Camel headers used by each component.
BB-192In Camel-ddsi component, the "networkInterfaces" option has been renamed to "networkInterface" and accepts only 1 interface name. Multi-homed hosts (with several interfaces) was actually badly supported.
BB-195Removed the "preprocessor" option from opensplice-idl-plugin since latest idlpp versions (since Vortex OpenSplice 6.4.1) removed the equivalent -c option.
BB-193Fix "java.null.NullPointerException" in camel-ddsi when receiving a message with a null payload (e.g. a message indicating an instance has been disposed).

Version 1.3.1

Report ID.Description
BB-149Add a 'readMode' option to camel-ospl to have the consumer endpoint using the DDS DataReader.read() operation instead of DataReader.take() operation.

Version 1.3.0

Report ID.Description
BB-92Add DDSI over TCP mode. NOTE: this is experimental. No dynamic discovery (static configuration of peers) and no NAT trasversal capabilities.
BB-140OpenSplice Gateway now uses the the same DDSI implementation than OpenSplice Mobile. It also uses OpenSplice Mobile's iShapes demo for it's own shapes-* examples. (WARNING: Java 7 is required for iShapes demo)
 BB-128Add 'networkInterfaces' option to camel-ddsi to choose the network insterfaces to use.
BB-143Add 'registerType' option to camel-ddsi to register the Topic type with another name that the classname.
BB-130Fix ResolveEndpointFailedException in camel-message-mode example.

Version 1.2.0

Report ID.Description
BB-90Add dynamic QoS for camel-ospl endpoint. See User Guide for more information.
BB-106Add support of fragmentation of large data in DDSI protocol implementation (used by camel-ddsi endpoint). This is transparent to user and is automatically activated for data larger than 1280 bytes.
BB-83Add examples of DDS bridging over TCP/HTTP/HTTPS/WebSocket using camel-ddsi endpoint (see examples/shapes-ddsi-bridges).
BB-115Add a graphical example of a graphical Web page polling DDS data via REST URLs (see examples/shapes-java).
BB-103Change the dependency to Apache Camel version 2.9.0.fuse-7-061. Note that OpenSplice Gateway 1.2.0 has also been successfully tested with versions 2.8.5, 2.9.3 and 2.10.0.
BB-119Add list of dependencies licenses in third_party_licenses.html file.
BB-102Using camel-ospl endpoint, some routes may cause a StackOverflowError for each message, with lot of calls to ClassLoader in stack trace.
BB-108Using camel-ddsi on Windows, when 2 Gateway processes are started on the same host with routes using the same DDS Domain, one of the process doesn't receive any DDS data.
BB-109Using camel-ddsi, a process might be blocked at the end of main() operation, because of pending resources.

Version 1.1.1

Report ID.Description
BB-78examples/shapes-ddsi compilation fails on Windows.

Version 1.1.0 – 1.0.0

Report ID.Description
BB-60Add a new Camel component based on Java DDSI implementation. See User Guide for more information.
BB-74Add creation of a Maven Repository package for offline installation and examples run. See Installation Guide for more information.
BB-8Add a new PingPong example (compatible with Vortex OpenSplice's PingPong example).
BB-10Add in shapes-java example an route using CEP (Complex Event Processing) with camel-esper component.
BB-67Add blocking behavior to the DDSPollingConsumer's receive() and receive(timeout) operations (receiveNoWait() operation keeps non-blocking behavior).
BB-72Change the separator character to be used in "partition" option for "dds:" URI. ',' (comma) has to be used instead of '%' ('%' is also the escape character in URIs).
BB-73Change the Camel version to 2.8.0-fuse-03-06.
BB-76With Vortex OpenSplice evaluation versions, the opensplice-idl-plugin fail to compile a valid IDL.
BB-29Obfuscate camel-ospl jar.
 BB-65DDS entities are not deleted at Camel route stop. And in DdsPollingConsumer, ReadCondition/QueryCondition objects are not deleted after the pull has finished.
BB-23After switch to Camel 2.7.1 chatroom-webservice example failed. Consequently it was removed from releases.
BB-59The ZIP delivery file contains directories in 777 mode.
BB-66Update copyright headers for 2012.
BB-57Provide support for 64 bit Windows and Solaris.
BB-56Change "BlendBox" name to "Gateway".
BB-54Documentation improvement.
BB-51Add a way for user to generate configuration information to be sent to support in case of troubles.
BB-52Importing a BlendBox Maven project in Eclipse causes following error: "Plugin execution not covered by lifecycle configuration: org.opensplice.b2:opensplice-idl-plugin:1.0.0:idl-compile".
BB-49In v1.0.0 the rlm/pom.xml has version 1.0.0 but the parent-pom/pom.xml depends on rlm version 9.1.3.

 

 

 

About Alison Maclean

View all posts by Alison Maclean →