A: See Connectivity Troubleshooting.
A: When Handler performs book resynchronization, it caches all the data received on incremental feeds. When the market is busy, number of cached messages may exceed configured limit defined by OnixS::CME::MarketData::HandlerSettings::incrementalMessageQueueMaxSize parameter value. So, to avoid 'PacketQueueOverflow' warnings, it's necessary to increase value of the noted parameter which equals to 10000 by default.
A: If you subscribe to the Book Updated, you'll always have a consistent book. Book Changed callbacks are designed for those who want to build and maintain books by themselves. Book Change is an elementary action over the order book and usually there're multiple changes inside single snapshot and/or incremental refresh. For this reason, book may not be valid between two changes. Only when all the changes are processed from the single network packet (message like snapshot and incremental refresh), book is considered as valid. Book Updated callbacks are called exactly at a time when all changes are processed and book appears to be valid and up-to-date.
For more information Building and Maintaining Books by Yourself topic.
A: For the implied eligible products, one may see the cross book momentarily and the book becomes normal after the next transaction at the engine. So it is possible to see the crossed book in the OnixS::CME::MarketData::ConsolidatedBookUpdateListener::onConsolidatedBookUpdated callback even when the market is in the opened state.
A: Security definition sent by Market Data Platform contains field DisplayFactor (tag 9787) representing the multiplier to convert the CME Globex display price to the conventional price.