Hello gents, could you please confirm that the following looks like a MAMA layer issue, or maybe our bridge is not acting properly? The issue: there is a subscription in process of activation or deact

Hi, What is an intended purpose of the advisory cause and platform info mechanizm in transport and subscription, please? Thank you. Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Otta

The messages I'm talking about are published on _MDDD.<bridge>.DATA_DICT So if a message 1) is coming on _MD.* and 2) its MamaFieldSubscMsgType is MAMA_SUBSC_* that is a subscription request, right? C

Hi Frank, I see these messages in a dictionary publish case, when MdSubscMsgType is a dictionary entry (yes, I know it's a reserved word and shouldn't be used, this was not my idea to use it). I can e

Could you please point me in the code where I would be able to see what notifications and under what conditions are generated by OpenMAMA from subscribers to publishers? Thank you in advance. Regards,

Hi, When a message has this field: MdSubscMsgType:61 and also it has this field: MdMsgType:1 am I right to assume that MdMsgType is the real message type? In other words, does MdMsgType take precedenc

see proton-c\include\proton\import_export.h, looks like PN_EXTERN gets resolved to __declspec(dllimport) Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace System

0.12.1 Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken

qpid-proton.dll I built doesn't have symbols from codec.h exported, so it look s like I'm missing qpid_proton_EXPORTS define, does it make sense? Thanks Dmitri Regards, Dmitri Fedorov Software Archite

Thanks Frank, sounds good ​Cheers Dmitri​

Hi Damian, For me the problem was in OpenMAMA, specifically, it was absence of clear and precise description of dependences: what's for the dependency is used, what versions for each platform and wher

Hi Frank, This approach makes sense to me because my goal from the beginning was to assign proper values to EVENT_HOME, PROTON_HOME and AVIS_HOME. Here is a branch I fixed to build with VS2015, I did

I've fixed the error, no big deal, my intention here is to understand if a) I'm not following instructions properly or b) the instructions need to be updated. You're the only person who can tell me if

Same error using the VS project file: 1> event.c 1>c:\program files (x86)\windows kits\10\include\10.0.10240.0\ucrt\time.h(39): error C2011: 'timespec': 'struct' type redefinition 1> c:\projects\ext\l

Frank, Now I'm puzzled by the other dependency: libevent. The OpenMAMA Wiki page you referred to suggests to build 1.4.x as libevent_code.lib, but openmama\mama\c_cpp\src\c\bridge\avis\avis.vcxproj re

This is 32-bit build reference, right? 64-bit AVIS build creates \platforms\windows\x64\$(Configuration) Do you build OpenMAMA 64-bit on Windows or I'm the only one who's doing it and I shouldn't do i

This is the structure of packages I'm referring to, none of them has "platforms" directory. Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no

Sorry Frank for the typo, the AVIS source of course, not axis Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no liability for the content of t

Yes, Frank, I get that, this is not what I'm asking, I'm asking where do I get the axis source that fits into this structure after compilation? Here: https://sourceforge.net/projects/avis/files/ I've

Thanks Frank, now I'm stuck on Avis dependency. avis.vcxproj refers to $(AVIS_HOME)\platforms\windows\Debug\avis.dll and $(AVIS_HOME)\platforms\windows\$(Configuration) both AVIS Windows client and a