Hi all,

I'm investigating an issue in a Solace proprietary product that uses an instance of MamdaOrderBookListener to keep track of orders and to populate recap messages.

During the investigation I've come across two different formats for recap messages coming from the MamdaOrderBook->populateRecap(MamaMsg& recapMsg) call: one has ask/bid strings and the other does not.

Where should I dig to find out why and how this happens?

In my test case the publisher generates eight price levels (four asks and for bids), and after a few tens of thousand messages, the first recap message format I see is:

[653]=PRICE:10.01
[654]=INT8:65
[655]=UINT32:1014500
[656]=UINT32:0
[657]=UINT16:2257
[658]=DATETIME:2017-01-04 22:55:57.428543
[681]=STRING:ask
[682]=UINT32:500
[683]=INT8:65
}, {

the second:

}, {
[653]=PRICE:10.01
[655]=UINT32:1006400
[656]=UINT32:0
[657]=UINT16:2221
[658]=DATETIME:2017-01-04 22:55:57.440543
[659]=INT16:0
}, {

[657] is the entry count wPlNumEntries, [681], [682] and [683] are wEntryId, wEntrySize and wEntryAction, and [659] (that is missing from the first recap message format) is wPlNumAttach.

T

​hank you in advance.​

Regards,

Dmitri Fedorov

Software Architect

Solace

Ottawa, ON Canada

Solace Corporation accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Corporation.

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