1. Openmama-Users
  2. Messages

Expanded

Topics Messages Polls
   Date   
OpenMAMA 6.3.2 Released

Frank Quinn
 

Hi Folks,

 

We are pleased to announce OpenMAMA 6.3.2 is finally here and has now propagated to Cloudsmith, Maven central etc!

 

Apologies for the delay, but it took us a little while to get our public documentation updated to reflect the latest changes and build instructions (because they were substantial).

 

Note in case you missed it, our API Reference and Developer guide documentation has been overhauled since the last release:

 

 

There are some key changes included in this release including:

 

 

This release includes new changes to support:

 

  • CentOS Stream 8
  • CentOS Stream 9
  • RHEL 8
  • RHEL 9
  • Ubuntu 22.04 LTS
  • Visual Studio 2022

 

And drops support for:

 

  • Fedora (we now favour CentOS stream for getting ahead of upstream RH changes)
  • CentOS 6 (EOL November 2020)
  • CentOS 8 (EOL December 2021)
  • Ubuntu 16.04 (EOL April 2021)

 

If there are any issues found, please report following the instructions here:

 

https://openmama.finos.org/openmama_raising_issues.html

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: https://cascadium.io

 
Re: CentOS 6 / RHEL 6 Support (Reply Needed)

Frank Quinn
 

Hi Folks,

 

Now that CentOS has been EOL for 16 months, could I ask for feedback again on the below please? 1, 2 or 3?

 

Cheers,

Frank

 

Frank Quinn, Cascadium | +44 (0) 28 8678 8015 | https://cascadium.io

 

From: Openmama-users@... <Openmama-users@...> On Behalf Of Frank Quinn via lists.openmama.org
Sent: 20 November 2020 09:30
To: openmama-dev@...; openmama-users@...
Subject: [Openmama-users] CentOS 6 / RHEL 6 Support (Reply Needed)

 

Hi Folks,

 

CentOS 6 is reaching its main EOL on the 30th November (10 days time), so I’d like to ask the community where they are in respect to migration.

 

Please feel free to reply to me either directly or via list with one of the below:

 

  1. CentOS 6? How quaint. Kill it with fire.
  2. We are moving off CentOS 6 and expect to be migrated away from it before the next OpenMAMA release in Summer.
  3. I think we’d need CentOS support for at least another year or so until all our systems migrate.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
OpenMAMA OMNM 1.0.0 Released

Frank Quinn
 

Hi Folks,

 

It has been a while since the last release but we’re pleased to announce the release of OpenMAMA OMNM 1.0.0. This release includes:

 

  • Complete interface compatibility with OpenMAMA
  • Complete unit test coverage for all official OpenMAMA unit tests
  • Platform support for all OpenMAMA supported platforms including Windows and OSX
  • A set of methods to support extending omnm for use in other payload bridges with reduced code required:
    • omnmmsgPayloadImpl_[gs]etExtenderClosure to allow the extender
      to attach their own internal object to the omnm payload
    • omnmmsgPayloadImpl_updateVectorMsgPayload to allow the extender
      to update vectors of messages without needing an intermediate
      mamaMsg for each submsg.

Release artifacts can be found here:

https://github.com/cascadium/OpenMAMA-omnm/releases

Or by running:

yum / apt upgrade openmama-omnm

From the OpenMAMA thirdparty repository hosted by our friends at cloudsmith:

https://cloudsmith.io/~openmama/repos/openmama-thirdparty/packages/

The first implementation based on this base bridge will be released soon too and adds support for msgpack.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
OpenMAMA Now Available on Homebrew (Mac / Linux)

Frank Quinn
 

That’s right Mac users – OpenMAMA has been approved and is now included in homebrew’s set of packages.

 

So to install OpenMAMA on a Mac, simply

 

brew update

brew install openmama

 

…and yes this will also work on the new Apple M1 machines.

 

This also has been verified as working with linuxbrew (if anyone uses that).

 

Any issues please raise an issue on the OpenMAMA github page!

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
CentOS 6 / RHEL 6 Support (Reply Needed)

Frank Quinn
 

Hi Folks,

 

CentOS 6 is reaching its main EOL on the 30th November (10 days time), so I’d like to ask the community where they are in respect to migration.

 

Please feel free to reply to me either directly or via list with one of the below:

 

  1. CentOS 6? How quaint. Kill it with fire.
  2. We are moving off CentOS 6 and expect to be migrated away from it before the next OpenMAMA release in Spring.
  3. I think we’d need CentOS support for at least another year or so until all our systems migrate.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
Announcing OZ: a production-quality, open-source transport for OpenMAMA using ZeroMQ

Bill Torpey
 

Everyone on this mailing list is already well acquainted with OpenMAMA's awesome-ness, but I want to let you know about something that makes OpenMAMA even more awesome.

One thing that has always been a trouble spot for OpenMAMA is the lack of a reliable, high-performance, open-source transport library. The AVIS bridge was little more than a toy, and while the Qpid bridge was an improvement, there has never been a production-quality, open-source transport bridge for OpenMAMA.

Until now.

NYFIX, a division of Itiviti AB, has recently released an open-source transport for OpenMAMA based on ZeroMQ which we are calling OZ. OZ has been in live production use supporting the NYFIX Marketplace since early March in our data centers in Europe, Asia and the U.S., processing roughly 50 million messages per day.

OZ was designed to support many of the most popular features of typical MOM's:

  • publish/subscribe messaging using topic-based addressing, supporting hierarchical topic namespaces and "wildcard" subscriptions;
  • request/reply (inbox) messaging for transactional interactions;
  • dynamic service discovery with minimal configuration;
  • broker-less architecture for reduced latency and optimum throughput;
  • self-describing messages (thanks to OpenMAMA-omnm).

We recently published a whitepaper describing OZ, but the more technical-minded will probably prefer to check out the docs and/or take a look at the sample code. (In particular, the examples use modern C++ constructs to provide a kinder, gentler introduction to OpenMAMA).

We're hopeful that the OpenMAMA community will find OZ helpful, and we look forward to working with everyone in the community to make OZ, and OpenMAMA itself, even better. We encourage everyone to check out OZ at https://github.com/nyfix/OZ.

Please contact me directly or raise an issue with any comments, suggestions, etc.
OpenMAMA 6.3.1 Released

Frank Quinn
 

Hi Folks,

 

We are pleased to announce OpenMAMA 6.3.1 is finally here and has now propagated to Cloudsmith, Maven central etc!

 

This is a maintenance release which fixes several outstanding bugs and introduces some new functionality.

 

  • Added experimental .NET core support (including C# on Linux)
  • Updated supported platforms to include CentOS 8, Ubuntu 18.04 LTS and Ubuntu 20.04 LTS
  • Added quickstart / start of tutorial code for all languages
  • Modernized JNI implementation to use javac -h rather than javah
  • Added json and normalized string methods for all language bindings (formerly reserved for only C)
  • Fix multithreaded builds in OpenMAMA and add "experimental" cloudsmith repository automatic upload
  • Added support for clang sanitizers
  • Added code for creating your own Vagrant box for OpenMAMA (and we uploaded our own)
  • Added ansible code for creating a demo environment
  • Fixed a few race conditions, leaks and bugs
  • Improved Mac Support

 

For a complete list of all 21 issues included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/11?closed=1

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
New OpenMAMA Website is Live!

Frank Quinn
 

Hi Folks,

 

After a successful testing period (thanks to all who were involved), we are delighted to announce the official launch the new OpenMAMA website which went live yesterday evening: https://openmama.org

 

We will be getting the word out on social media so please like / share our posts to extend our reach! Also please update any existing links etc. to the OpenMAMA website where appropriate.

 

The site is a complete overhaul and has several key improvements over the former site beyond aesthetics:

 

  • It is responsive
  • It is a static, bloat-free website so it should load very quickly
  • You can submit your own suggested changes to the site via pull request because it's all on github
  • It merges the documentation and main marketing website into one
  • It generally tries to de-duplicate information and the content has had a general refresh

 

If there are any issues please raise them at https://github.com/OpenMAMA/openmama.github.io/issues and we hope you enjoy the new site! As usual, we’ll be keeping an eye on gitter if you have any immediate feedback / concerns.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
Re: Last call for OpenMAMA 6.3.1 release candidate

Frank Quinn
 

Hi Folks,

 

Looks like a number of issues are still coming in and I have identified a few things that I want to get in myself, so I’m going to push this back 1 week to the weekend commencing 28-Aug 2020.

 

Cheers,

Frank

Frank Quinn, Cascadium | +44 (0) 28 8678 8015 | http://cascadium.io

 

From: Frank Quinn
Sent: 18 August 2020 23:12
To: openmama-users@...
Subject: Last call for OpenMAMA 6.3.1 release candidate

 

Hi Folks,

 

I plan on taking a cut for OpenMAMA 6.3.1 RC1 over the coming weekend (21-Aug 2020). If anyone has anything they want to submit before then please let me know so I can delay the cut if necessary, otherwise I will continue as planned.

 

This release includes some changes to support:

 

  • CentOS 8
  • Fedora 31
  • Fedora 32
  • Ubuntu 20.04 LTS

 

It also effectively drops support for the now EOL:

 

  • Fedora 28
  • Fedora 29
  • Ubuntu 14.04 LTS

 

This is in preparation for a RC that will be cut within the next few weeks which is now set up to include RPMs and Debian packages for these modern distros to make installation easy, take care of dependencies etc.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
Last call for OpenMAMA 6.3.1 release candidate

Frank Quinn
 

Hi Folks,

 

I plan on taking a cut for OpenMAMA 6.3.1 RC1 over the coming weekend (21-Aug 2020). If anyone has anything they want to submit before then please let me know so I can delay the cut if necessary, otherwise I will continue as planned.

 

This release includes some changes to support:

 

  • CentOS 8
  • Fedora 31
  • Fedora 32
  • Ubuntu 20.04 LTS

 

It also effectively drops support for the now EOL:

 

  • Fedora 28
  • Fedora 29
  • Ubuntu 14.04 LTS

 

This is in preparation for a RC that will be cut within the next few weeks which is now set up to include RPMs and Debian packages for these modern distros to make installation easy, take care of dependencies etc.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
Use of multiple bridges

Sergey Emantayev
 

I'm exploring an option for my MAMDA application to receive market data from multiple bridges. However, the Mamda initialisation API like MamdaCommonFields::setDictionary is confusing me because it is the static function accepting a single dictionary. Different bridges may have different dictionaries and it seems to work with only a single bridge. Is there any solution or workaround?

Best Regards,
Sergey Emantayev
OpenMAMA 6.2.3 Released

Frank Quinn <fquinn@...>
 

Hi Folks,

 

We are pleased to announce the final release of OpenMAMA 6.2.3 is now available:

 

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.2.3-release

 

This is a hotfix release to address two key issues which were discovered as part of the recent 6.2.2 release:

 

* Restore mamaSubscription RecoverGaps functions accidentally removed in the last release

* Restore missing wombat portability headers in 6.2.2 Release

 

For a complete list of the issues included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/9?closed=1

 

Cheers,

Frank

 

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
Re: OpenMAMA 6.2.2 Released

Damian Maguire
 

Thanks for this Frank, some fantastic work gone into this one. Great to have the release available in so many of the standard repos now, and with Cmake support getting bedded in it should be a lot easier for people to build from scratch as well (big thanks to Victor for all the effort on that one).


Huge amount of other work in there as well, so thanks to all the contributors along the way.


Thanks,


Damian


DAMIAN MAGUIRE 

Senior Sales Engineer

Vela

 

O. +44 289 568 0298  

M. +44 783 584 4770 

dmaguire@... 

 

Adelaide Exchange Building, 2nd Floor, 24-26 Adelaide Street, Belfast, BT2 8GD  

tradevela.com | @tradevela


1518792739120_PastedImage



From: Openmama-dev@... <Openmama-dev@...> on behalf of Frank Quinn <fquinn@...>
Sent: 02 July 2018 21:11
To: openmama-dev@...; openmama-users@...
Subject: [Openmama-dev] OpenMAMA 6.2.2 Released
 

Hi Folks,

 

We are pleased to announce the final release of OpenMAMA 6.2.2 is now available:

 

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.2.2-release

 

Note that for the first time, a OpenMAMA generally available release is now available via Maven Central, Microsoft’s vcpkg and yum repositories (via Cloudsmith).

 

Documentation will be coming in the following weeks with more details including how to use our new experimental cmake build system!

 

This is a maintenance release which fixes several outstanding bugs and introduces some new functionality.

 

Key features include:

 

  • Introduction of pluggable DQ strategies (Market Data Subscription recovery mechanisms). See https://openmama.github.io/openmama_rfc_dq_pluggability.html
  • Added new methods mamaMsg_toJsonString and mamaMsg_toNormalizedString
  • OpenMAMA source structure moved to maven and build system moved to gradle
  • Cmake support now available (experimental). Note it will replace scons in the next release and supports Windows, Linux and OSX
  • OpenMAMA added to Microsoft vcpkg for easy nuget packaging and building from source
  • OpenMAMA Integration headers now available to allow developers to build plugins and bridges without access to the source code. See https://openmama.github.io/openmama_bridge.html#openmama-integration-headers.
  • Added implementation for mamaPrice_setFromString
  • MamaPrice can now support decimal point precision up to 16 places
  • Implement MamaFieldCache in JNI enhancement
  • Support for setting mamaDateTime with pre-1970 dates on Unix platforms
  • Removal of Visual Studio compiler warnings
  • Added Appveyor integration for CI
  • Add support for autoloading payload bridges from config

 

For a complete list of all 55 issues included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/8?closed=1

 

A special thanks to all developers, contributors and testers who helped is getting this out door.

 

Cheers,

Frank

 

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 


The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. Vela Trading Systems LLC

OpenMAMA 6.2.2 Released

Frank Quinn <fquinn@...>
 

Hi Folks,

 

We are pleased to announce the final release of OpenMAMA 6.2.2 is now available:

 

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.2.2-release

 

Note that for the first time, a OpenMAMA generally available release is now available via Maven Central, Microsoft’s vcpkg and yum repositories (via Cloudsmith).

 

Documentation will be coming in the following weeks with more details including how to use our new experimental cmake build system!

 

This is a maintenance release which fixes several outstanding bugs and introduces some new functionality.

 

Key features include:

 

  • Introduction of pluggable DQ strategies (Market Data Subscription recovery mechanisms). See https://openmama.github.io/openmama_rfc_dq_pluggability.html
  • Added new methods mamaMsg_toJsonString and mamaMsg_toNormalizedString
  • OpenMAMA source structure moved to maven and build system moved to gradle
  • Cmake support now available (experimental). Note it will replace scons in the next release and supports Windows, Linux and OSX
  • OpenMAMA added to Microsoft vcpkg for easy nuget packaging and building from source
  • OpenMAMA Integration headers now available to allow developers to build plugins and bridges without access to the source code. See https://openmama.github.io/openmama_bridge.html#openmama-integration-headers.
  • Added implementation for mamaPrice_setFromString
  • MamaPrice can now support decimal point precision up to 16 places
  • Implement MamaFieldCache in JNI enhancement
  • Support for setting mamaDateTime with pre-1970 dates on Unix platforms
  • Removal of Visual Studio compiler warnings
  • Added Appveyor integration for CI
  • Add support for autoloading payload bridges from config

 

For a complete list of all 55 issues included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/8?closed=1

 

A special thanks to all developers, contributors and testers who helped is getting this out door.

 

Cheers,

Frank

 

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
OpenMAMA-6.2.2-rc2 Now Available

Frank Quinn <fquinn@...>
 

Hi Folks,

 

We were planning on releasing today but a pull request landed yesterday containing some bugfixes for the recently added plugin code which I have deemed as necessary for this release, so I have now cut OpenMAMA 6.2.2-rc2 which can be found here:

 

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.2.2-rc2

 

Considering this is bugfix only, the release candidate window will be one week, making the target release date (all being well) 28th June.

 

I encourage all application and bridge developers to rigorously test this new release with their software especially with respect to the market data subscription life cycle.

 

If there are any further incoming changes please advise me asap to see if the above dates need to be revised.

 

Cheers,

Frank

 

Frank Quinn, Cascadium | +44 (0) 28 8678 8015 | http://cascadium.io

 

From: Frank Quinn
Sent: 13 June 2018 20:36
To: 'openmama-dev@...' <openmama-dev@...>; 'openmama-users@...' <openmama-users@...>
Subject: RE: OpenMAMA-6.2.2-rc1 Now Available

 

Hi Folks,

 

Hope testing is going well!

 

We’ve just submitted a change to correct a few unit test compiler warnings and memory leaks recently introduced but nothing which impacts core code so there’s no current reason to extend the RC window.

 

Just a reminder that we’re going into the final week of testing here so if anyone has spotted anything unusual please speak up now if you want a fix to make it into this release!

 

Cheers,

Frank

 

Frank Quinn, Cascadium | +44 (0) 28 8678 8015 | http://cascadium.io

 

From: Frank Quinn
Sent: 29 May 2018 21:07
To: 'openmama-dev@...' <openmama-dev@...>; 'openmama-users@...' <openmama-users@...>
Subject: OpenMAMA-6.2.2-rc1 Now Available

 

Hi Folks,

 

We are pleased to announce the first release candidate for OpenMAMA 6.2.2 is now available:

 

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.2.2-rc1

 

This is a maintenance release which fixes several outstanding bugs and introduces some new functionality.

 

Key features include:

 

  • Introduction of pluggable DQ strategies (Market Data Subscription recovery mechanisms). See https://openmama.github.io/openmama_rfc_dq_pluggability.html
  • Added new methods mamaMsg_toJsonString and mamaMsg_toNormalizedString
  • OpenMAMA source structure moved to maven and build system moved to gradle
  • Cmake support now available (experimental). Note it will replace scons in the next release and supports Windows, Linux and OSX
  • OpenMAMA added to Microsoft vcpkg for easy nuget packaging and building from source
  • OpenMAMA Integration headers now available to allow developers to build plugins and bridges without access to the source code. See https://openmama.github.io/openmama_bridge.html#openmama-integration-headers.
  • Added implementation for mamaPrice_setFromString
  • MamaPrice can now support decimal point precision up to 16 places
  • Implement MamaFieldCache in JNI enhancement
  • Support for setting mamaDateTime with pre-1970 dates on Unix platforms
  • Removal of Visual Studio compiler warnings
  • Added Appveyor integration for CI
  • Add support for autoloading payload bridges from config

 

For a complete list of all 54 issues included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/8?closed=1

 

Thank you all in advance for your help in testing - if you spot any issues, please follow our guidelines for raising an issue, or even better, follow our guidelines for raising a patch.

 

Since the release is significant, the testing period will be 3 weeks from today making the target release date 20th June and everyone is invited to try it out - binary releases are available at the link above.

 

If critical issues are found and not resolved before this date, we will continue to go through weekly release candidates until have a stable release ready.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
Re: OpenMAMA-6.2.2-rc1 Now Available

Frank Quinn <fquinn@...>
 

Hi Folks,

 

Hope testing is going well!

 

We’ve just submitted a change to correct a few unit test compiler warnings and memory leaks recently introduced but nothing which impacts core code so there’s no current reason to extend the RC window.

 

Just a reminder that we’re going into the final week of testing here so if anyone has spotted anything unusual please speak up now if you want a fix to make it into this release!

 

Cheers,

Frank

 

Frank Quinn, Cascadium | +44 (0) 28 8678 8015 | http://cascadium.io

 

From: Frank Quinn
Sent: 29 May 2018 21:07
To: 'openmama-dev@...' <openmama-dev@...>; 'openmama-users@...' <openmama-users@...>
Subject: OpenMAMA-6.2.2-rc1 Now Available

 

Hi Folks,

 

We are pleased to announce the first release candidate for OpenMAMA 6.2.2 is now available:

 

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.2.2-rc1

 

This is a maintenance release which fixes several outstanding bugs and introduces some new functionality.

 

Key features include:

 

  • Introduction of pluggable DQ strategies (Market Data Subscription recovery mechanisms). See https://openmama.github.io/openmama_rfc_dq_pluggability.html
  • Added new methods mamaMsg_toJsonString and mamaMsg_toNormalizedString
  • OpenMAMA source structure moved to maven and build system moved to gradle
  • Cmake support now available (experimental). Note it will replace scons in the next release and supports Windows, Linux and OSX
  • OpenMAMA added to Microsoft vcpkg for easy nuget packaging and building from source
  • OpenMAMA Integration headers now available to allow developers to build plugins and bridges without access to the source code. See https://openmama.github.io/openmama_bridge.html#openmama-integration-headers.
  • Added implementation for mamaPrice_setFromString
  • MamaPrice can now support decimal point precision up to 16 places
  • Implement MamaFieldCache in JNI enhancement
  • Support for setting mamaDateTime with pre-1970 dates on Unix platforms
  • Removal of Visual Studio compiler warnings
  • Added Appveyor integration for CI
  • Add support for autoloading payload bridges from config

 

For a complete list of all 54 issues included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/8?closed=1

 

Thank you all in advance for your help in testing - if you spot any issues, please follow our guidelines for raising an issue, or even better, follow our guidelines for raising a patch.

 

Since the release is significant, the testing period will be 3 weeks from today making the target release date 20th June and everyone is invited to try it out - binary releases are available at the link above.

 

If critical issues are found and not resolved before this date, we will continue to go through weekly release candidates until have a stable release ready.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
OpenMAMA-6.2.2-rc1 Now Available

Frank Quinn <fquinn@...>
 

Hi Folks,

 

We are pleased to announce the first release candidate for OpenMAMA 6.2.2 is now available:

 

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.2.2-rc1

 

This is a maintenance release which fixes several outstanding bugs and introduces some new functionality.

 

Key features include:

 

  • Introduction of pluggable DQ strategies (Market Data Subscription recovery mechanisms). See https://openmama.github.io/openmama_rfc_dq_pluggability.html
  • Added new methods mamaMsg_toJsonString and mamaMsg_toNormalizedString
  • OpenMAMA source structure moved to maven and build system moved to gradle
  • Cmake support now available (experimental). Note it will replace scons in the next release and supports Windows, Linux and OSX
  • OpenMAMA added to Microsoft vcpkg for easy nuget packaging and building from source
  • OpenMAMA Integration headers now available to allow developers to build plugins and bridges without access to the source code. See https://openmama.github.io/openmama_bridge.html#openmama-integration-headers.
  • Added implementation for mamaPrice_setFromString
  • MamaPrice can now support decimal point precision up to 16 places
  • Implement MamaFieldCache in JNI enhancement
  • Support for setting mamaDateTime with pre-1970 dates on Unix platforms
  • Removal of Visual Studio compiler warnings
  • Added Appveyor integration for CI
  • Add support for autoloading payload bridges from config

 

For a complete list of all 54 issues included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/8?closed=1

 

Thank you all in advance for your help in testing - if you spot any issues, please follow our guidelines for raising an issue, or even better, follow our guidelines for raising a patch.

 

Since the release is significant, the testing period will be 3 weeks from today making the target release date 20th June and everyone is invited to try it out - binary releases are available at the link above.

 

If critical issues are found and not resolved before this date, we will continue to go through weekly release candidates until have a stable release ready.

 

Cheers,

Frank

 

Frank Quinn

Cascadium

T: +44 (0) 28 8678 8015

E: fquinn@...

W: http://cascadium.io

 
Re: [Openmama-dev] Let's test cmake support

Frank Quinn <fquinn@...>
 

Hi folks,

Further to this, we have now wired up with C#, install rules and unit tests on Linux, Windows and even native OSX (with some recent changes).

This is a huge step because it effectively outsources compiler support which we effectively had to manage ourselves with our previous scons infrastructure as well as fight with python environments.

With that in mind I have now raised https://github.com/OpenMAMA/OpenMAMA/pull/361 which will hopefully make it into next soon!

After the next release goes out (which I propose is soon), we can look at making cmake the default for CI and the release following that one.

Cheers,
Frank

On 27 Apr 2018 10:05, Victor Maleyev <imnotmindlin@...> wrote:
Hi guys,

Me and Frank made some efforts to support CMake build system: it builds MAMA on Linux and Windows. Unfortunately it is not in trunk yet but I desperately need any feedback on how it works to make it stable and ready for release. Just clone the repo from here: https://github.com/fquinner/OpenMAMA/tree/feature-cmake-support and try build it like this:
mkdir build
cmake ..
make

Make sure that flex, Apache portable runtime and gradle are installed.

Feel free to mail me if issues are found.

[Openmama-dev] Let's test cmake support

Victor Maleyev
 

Added openmama-users

-------- Пересылаемое сообщение--------
27.04.2018, 12:05, "Victor Maleyev" <imnotmindlin@...>:

Hi guys,

Me and Frank made some efforts to support CMake build system: it builds MAMA on Linux and Windows. Unfortunately it is not in trunk yet but I desperately need any feedback on how it works to make it stable and ready for release. Just clone the repo from here: https://github.com/fquinner/OpenMAMA/tree/feature-cmake-supp… and try build it like this:
mkdir build
cmake ..
make

Make sure that flex, Apache portable runtime and gradle are installed.

Feel free to mail me if issues are found.




-------- Завершение пересылаемого сообщения --------
Re: [Openmama-dev] Did MAMAIgnoreDeprecatedOpen ever work on Linux? [I]

Frank Quinn <fquinn.ni@...>
 

Hi Yury,

Yes that method is deprecated because OpenMAMA prefers dynamic loading methods now (so that payloads don't need to be registered in OpenMAMA's core code to load or depend on magic characters).

Have you looked at mamaMsg_createForPayloadBridge? It should do the same thing, but accepts a payload bridge rather than a char identifier and is not deprecated.

Damian also provided some helper functions included 6.2.1 to help look up bridges by name which might be helpful for lookup and cache, including mama_getPayloadBridge.

Cheers,
Frank

On Tue, Oct 3, 2017 at 10:07 AM, Yury Batrakov <yury.batrakov@...> wrote:

Classification: For internal use only

Hey Damian,

 

OK, thank you for clarification. The reason why I thought that deprecation warnings should be deleted automatically (after defining MAMA_DLL and BRIDGE preprocessor variables) is the following declaration of mamaMsg_createForPayload

MAMAIgnoreDeprecatedOpen

MAMAExpDeprecatedDLL(

        "mamaMsg_createForPayload has been deprecated, use dynamic loading instead!")

extern mama_status

mamaMsg_createForPayload (mamaMsg* msg, const char id);

MAMAIgnoreDeprecatedClose

 

The background of this question is: I’m writing a middleware bridge which always has to create messages for specific payload - it’s a problem because mamaMsg_createForPayload is deprecated and mamaMsg_create creates messages for “default” payload - the payload initialized by a first bridge created by OpenMAMA. This will be a problem when two or more bridges are loaded to a process.

 

 

From: Damian Maguire [mailto:dmaguire@...]
Sent: Tuesday, October 03, 2017 10:27 AM
To: Yury Batrakov <yury.batrakov@...>; openmama-users <openmama-users@lists.openmama.org>; openmama-dev <openmama-dev@....org>
Subject: Re: Did MAMAIgnoreDeprecatedOpen ever work on Linux?

 

Hey Yury,

 

I'm not sure the behaviour you're describing is an issue - the purpose of the pragma's is to allow you to use 'deprecated' features of the API without generating warnings, rather than disable the deprecation completely. For example, when we implemented dynamic loading, we deprecated the 'mamaPayloadType' here. However, in order to support legacy clients, we continue to use the type within the MAMA codebase. We generally aim to be 'warning free' in the code, and understand the risks associated with using the type, so where we make use of mamaPayloadType we mark them with MamaIgnoreDeprecatedOpen and MamaIgnoreDeprecatedClose pragma's. This disables the deprecation specific warnings at those sites - for example, here.

 

Using your code, the equivalent would be:

 

int __attribute__((deprecated)) b() {

   return 0;

}

 

int main() {

        printf("GCC %d %d\n" , __GNUC__, __GNUC_MINOR__);

MamaIgnoreDeprecatedOpen

        b();

MamaIgnoreDeprecatedClose

        return 0;

}

 

Which shouldn't warn about the use of b();.

 

Let me know if that makes sense, or if you have further questions around this.

 

Thanks,

 

Damian

 

 

DAMIAN MAGUIRE 

Senior Sales Engineer 

 

 

Adelaide Exchange Building, 2nd Floor, 24-26 Adelaide Street, Belfast, BT2 8GD  

velatradingtech.com | @vela_tt

 

 

From: openmama-dev-bounces@lists.openmama.org <openmama-dev-bounces@lists.openmama.org> on behalf of Yury Batrakov <yury.batrakov@...>
Sent: 02 October 2017 17:16
To: openmama-users; openmama-dev
Subject: [Openmama-dev] Did MAMAIgnoreDeprecatedOpen ever work on Linux?

 

Classification: Public

Hi team,

 

Is MAMAIgnoreDeprecatedOpen supposed to work for Linux with gcc > 4.6?

See the following example:

 

// Next 3 lines were copied from wombat/…/linux/port.h

_Pragma ("GCC diagnostic push")

_Pragma ("GCC diagnostic ignored \"-Wdeprecated\"")

_Pragma ("GCC diagnostic ignored \"-Wdeprecated-declarations\"")

 

int __attribute__((deprecated)) b() {

   return 0;

}

 

_Pragma ("GCC diagnostic pop")

 

int main() {

        printf("GCC %d %d\n" , __GNUC__, __GNUC_MINOR__);

        b();

        return 0;

}

 

When compiling with 4.8 it shows the following warnings anyway:

/opt/gcc/gcc-4.8.1/bin/g++ -Wall -Wextra 123.c

123.c: In function ‘int main()’:

123.c:15:9: warning: ‘int b()’ is deprecated (declared at 123.c:7) [-Wdeprecated-declarations]

         b();

         ^

123.c:15:11: warning: ‘int b()’ is deprecated (declared at 123.c:7) [-Wdeprecated-declarations]

         b();

           ^

 

But if we place those pragmas around invocation of b() (not around the definition) all warnings go away



---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.


The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. Vela Trading Technologies LLC



---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.

_______________________________________________
Openmama-dev mailing list
Openmama-dev@....org
https://lists.openmama.org/mailman/listinfo/openmama-dev
1 - 20 of 235