Handling client update when snapshot not present

[giuseppe.corti]

Hi Doraintech,

The messages of the first type, "Unexpected snapshot event for COMMAND item user1_fills", are due to updates with the isSnaspshot flag set to true when the server has already determined the 'End Of Snapshot'. The update is still propagated to the client but with isSnapshot set to false.

The messages of the second type, "Unexpected UPDATE event for key ... . Event propagated as an ADD command.", are due to updates with the field command set to UPDATE for keys that actually have not been added to the Item with an event type ADD. The server in this case accepts the update changing the field command from UPDATE to ADD.

It is absolutely correct that all snapshot events for a command Item should be ADD.

I'm quite puzzled about the behavior that you are experiencing. In order to check the dynamics underway in your case, please could you arrange a test like this:

1. Shut down the Lightstreamer server and your Adapters;
2. Set these levels in the log configuration file (lightstreamer_log_conf.xml):
   
   • <logger name="LightstreamerProxyAdapters" level="DEBUG"> (for Lightstreamer 6)
   • <logger name="com.lightstreamer.adapters.remote" level="DEBUG"> (for Lightstreamer 5)
   • <logger name="LightstreamerLogger.subscriptions" level="DEBUG"/>
   • <logger name="LightstreamerLogger.pump" level="DEBUG"/>
3. Restart the Lightstreamer server and your Adapters;
4. Open only one client (and if it is possible perform only a single subscription for the Item involved);

From the log we should understand exactly what happens to your updates.

Regards,
Giuseppe

[doraintech]

Hi Giuseppe,

Please find the logs attached.

I have done a find and replace to remove some sensitive data but that should not make any difference to the part you are interested in.

Thanks for your help.

Doraintech