Hi folks - a reminder that we are going into the final week of this RC -if any major issues are spotted please raise as a priority!

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

Hi Folks, We (finally) have a new RC ready for testing with compiled artifacts for supported platforms – check it out:

Hi Folks, Quick reminder about the invitation below, and to thank everyone who has checked it out already (I can see a noticeable increase in traffic since sending this out so I know you folks are

Hi Folks, It is with great pleasure that I can declare that a new website is on its way. It is currently hosted at https://openmama.github.io as a preview version (the former documentation

Hi Folks, The default branch for OpenMAMA has now been set to “next”. Looks a little more lively already😊 If anyone runs into any issues, let me know. Hopefully overall this will make

Sounds quite sensible to me, Frank. Nigel Nigel Phelan | Corporate & Investment Bank | Market Data Services | J.P. Morgan

Hi Folks, I would like to propose that we change the OpenMAMA github default git branch to “next” instead of “master”. This would mean that: When you visit our github page, you will

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

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

Hi Folks, I have just pushed some changes into the next branch which add some changes to support: CentOS 8 Ubuntu 20.04 It also effectively drops support for the now EOL: Fedora

Hi Frank, Thanks for raising the issue in Github. We were able to reproduce this issue on a Linux (RH6) server using mamalistenc.c to subscribe to ~5000 symbols with the tick42rmds middleware

That's what the change should do - its a reference count that defers cleanup until the last reference has been released (since both the jvm GC and the bridge thread could both hit this code). It also

Hi Frank Does this actually address the issue with prematurely releasing the lock? Wouldn’t it be safer, as Mike suggested, to allow the thread that holds the lock to mark the object for

Hi Mike – did you have any joy with testing this one? Frank Quinn,Cascadium |+44 (0) 28 8678 8015| http://cascadium.io

Hi Mike, Have raised https://github.com/OpenMAMA/OpenMAMA/issues/411 For follow up on this one – let’s track there for paper trail / release note reference etc. Could you add some details

Hi OpenMAMA Dev, We have encountered a deadlock situation in mamaSubscription’s and mamaTransport’s teardown logic due to lock ordering when destroying their underlying mamaPublisher. We are

Classification: Public Hi Frank, I confirm that with your change I can reproduce the deadlock I described earlier: (gdb) info threads Id Target Id Frame 6 Thread

Classification: Public Hi Frank, Thank you for looking into this issue. Testing this change will take some time, but I think this change would introduce a deadlock due to change in locking

Hi Igor, can you try out this branch please? https://github.com/fquinner/OpenMAMA/tree/feature/subscription-throttle-lock-scope-reduction Cheers, Frank Frank Quinn,Cascadium | +44 (0) 28