Some changes have just been added to the origin/next branch! [fquinn.ni] PLAT-1189: Reserve fields tidyup (#303) mama/c_cpp/src/c/reservedfields.c[fquinn.ni] [COMMON] Fix potential buffer overflow in

Some changes have just been added to the origin/next branch! [fquinn.ni] Allows MamdaOrderBookWriter to add epoch 0 to book messages.

Some changes have just been added to the origin/next branch! [fquinn.ni] [MAMA] Off-by-one error in endpointpool (#307) mama/c_cpp/src/c/bridge/qpid/endpointpool.c Results for

Some changes have just been added to the origin/next branch! [fquinn.ni] Add missing qpid transport property (#308) mama/c_cpp/src/examples/mama.properties Results for OpenMAMA_Snapshot_Linux CI run

Some changes have just been added to the origin/next branch! [fquinn.ni] [MAMA] Add ability to suppress logging of payload load failure. (#306) mama/c_cpp/src/c/mama.c Results for

Some changes have just been added to the origin/next branch! [fquinn.ni] [MAMA] Add logging of thread names during creation (#305) mama/c_cpp/src/c/queue.c mama/c_cpp/src/c/mama.c Results for

Some changes have just been added to the origin/next branch! [fquinn.ni] [CAPTUREREPLAY] code cleanup and symbol file support

Some changes have just been added to the origin/next branch! [fquinn.ni] Fixed crash in MamdaTradeTicker (#296) mama/dotnet/src/cs/MamaMsgField.cs Results for OpenMAMA_Snapshot_Linux CI run with

Thanks Yury, Raised https://github.com/OpenMAMA/OpenMAMA/issues/300 so we don't forget to get this sorted. Cheers, Frank

Some changes have just been added to the origin/next branch! [fquinn.ni] [MAMA] Add comments to the DQ Publisher Manager headers (#299) mama/c_cpp/src/c/mama/dqpublishermanager.h Results for

Some changes have just been added to the origin/next branch! No changes Results for OpenMAMA_Snapshot_Windows CI run with latest changes: CI Project Name: OpenMAMA_Snapshot_Windows Build Number:

Classification: Public Hi guys, There is a copy-paste error in mamaSubscription_getSubjectContext function that leads to crash on subscription destroy in case if issue symbol differs that the symbol

Classification: Public Hi, Tom. As Frank suggested, I switched our app from destroy () to destroyEx() (MamaSubscription), but I still get a segmentation fault. I think the reason of segfault is

Yes we call back on the bridge’s thread. We don’t queue the message, we leave the client code to do that if it wants to. This is by design.

Classification: Public Hi, Tom. I noticed, that comparing to qpid bridge(that comes with openmama sources), tick42rmds calls mamaSubscription_processMsg() method from separate thread and not

Classification: Public Hi Tom, We are using version 1.3. As I see from latest github code the problem still exists. See RMDSBridgeSubscription::OnMessage method: if (isShutdown_ || ((0 !=

Hi Yury, Konstantin Are you using the current github version of the bridge code? We looked at and fixed some of the issues around locking the subscription destroy some time back. It would be good to

Apologies, I misread the part in the first email where it mentions mamaSubscription_destroy from arbitrary threads. If you're calling mamaSubscription_destroy from a thread which was not the same

Classification: Public Hi, guys. I'm working on the issue with Yury. I spotted the deadlock possibility during debugging tick42rmds bridge crash on unsubscribe, will be interested knowing the

Classification: Public Hi Frank, Let me answer your question in random order :) 2. It looks like a designed behavior of RMDS bridge - callbacks are invoked in a thread servicing transport events