Files

82 lines
28 KiB
HTML

<!-- HTML header for doxygen 1.8.11-->
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.11"/>
<title>OnixS C++ CME Market Data Handler: Pages/FAQ.md Source File</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
<link href="onixs-doxygen.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript">
$(window).scroll(function() {
if ($(this).scrollTop() > 1)
{
$('header').addClass("sticky");
}
else
{
$('header').removeClass("sticky");
}
});
</script>
</head>
<body>
<header>
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td id="projectlogo"><a href="http://www.onixs.biz"><img alt="Logo" src="onixs.svg"/></a></td>
<td style="padding-left: 0.5em;">
<div id="projectname">OnixS C++ CME Market Data Handler
&#160;<span id="projectnumber">4.8.0.10</span>
</div>
<div id="projectbrief">API documentation</div>
</td>
</tr>
</tbody>
</table>
</div>
</header>
<div id="wrapper">
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<!-- end header part -->
<!-- Generated by Doxygen 1.8.11 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Home</span></a></li>
<li><a href="modules.html"><span>Contents</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li class="current"><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
<div id="navrow2" class="tabs2">
<ul class="tablist">
<li><a href="files.html"><span>File&#160;List</span></a></li>
<li><a href="globals.html"><span>File&#160;Members</span></a></li>
</ul>
</div>
</div><!-- top -->
<div class="header">
<div class="headertitle">
<div class="title">Pages/FAQ.md</div> </div>
</div><!--header-->
<div class="contents">
<a href="FAQ_8md.html">Go to the documentation of this file.</a><div class="fragment"><div class="line"><a name="l00001"></a><span class="lineno"> 1</span>&#160;\addtogroup faq </div><div class="line"><a name="l00002"></a><span class="lineno"> 2</span>&#160;</div><div class="line"><a name="l00003"></a><span class="lineno"> 3</span>&#160;\brief Frequently asked questions.</div><div class="line"><a name="l00004"></a><span class="lineno"> 4</span>&#160;</div><div class="line"><a name="l00005"></a><span class="lineno"> 5</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00006"></a><span class="lineno"> 6</span>&#160;</div><div class="line"><a name="l00007"></a><span class="lineno"> 7</span>&#160;\section faq-handler-single-channel Can more than one channel per Handler be processed? Alternatively, are multiple Handler instances necessary?</div><div class="line"><a name="l00008"></a><span class="lineno"> 8</span>&#160;</div><div class="line"><a name="l00009"></a><span class="lineno"> 9</span>&#160;One instance of OnixS::CME::MDH::Handler processes market data for a single </div><div class="line"><a name="l00010"></a><span class="lineno"> 10</span>&#160;channel only. Users must create multiple instances of the Handler to process </div><div class="line"><a name="l00011"></a><span class="lineno"> 11</span>&#160;data from multiple channels.</div><div class="line"><a name="l00012"></a><span class="lineno"> 12</span>&#160;</div><div class="line"><a name="l00013"></a><span class="lineno"> 13</span>&#160;[Permanent link to the answer](@ref faq-handler-single-channel)</div><div class="line"><a name="l00014"></a><span class="lineno"> 14</span>&#160;</div><div class="line"><a name="l00015"></a><span class="lineno"> 15</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00016"></a><span class="lineno"> 16</span>&#160;</div><div class="line"><a name="l00017"></a><span class="lineno"> 17</span>&#160;\section faq-handler-securities-subscribed Is the Handler implicitly subscribed to all instruments of the specified channel? Will it receive security definitions for all instruments of this channel?</div><div class="line"><a name="l00018"></a><span class="lineno"> 18</span>&#160;</div><div class="line"><a name="l00019"></a><span class="lineno"> 19</span>&#160;Yes, exactly.</div><div class="line"><a name="l00020"></a><span class="lineno"> 20</span>&#160;</div><div class="line"><a name="l00021"></a><span class="lineno"> 21</span>&#160;[Permanent link to the answer](@ref faq-handler-securities-subscribed)</div><div class="line"><a name="l00022"></a><span class="lineno"> 22</span>&#160;</div><div class="line"><a name="l00023"></a><span class="lineno"> 23</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00024"></a><span class="lineno"> 24</span>&#160;</div><div class="line"><a name="l00025"></a><span class="lineno"> 25</span>&#160;\section faq-filtering How does instrument/group filtering work? Why would we want to do this?</div><div class="line"><a name="l00026"></a><span class="lineno"> 26</span>&#160;</div><div class="line"><a name="l00027"></a><span class="lineno"> 27</span>&#160;Filtering (instrument selection) is useful when market data required for </div><div class="line"><a name="l00028"></a><span class="lineno"> 28</span>&#160;specific instruments only. Instrument selection is like an inclusive </div><div class="line"><a name="l00029"></a><span class="lineno"> 29</span>&#160;whitelist. E.g., if security A is selected, security-related events </div><div class="line"><a name="l00030"></a><span class="lineno"> 30</span>&#160;(members of OnixS::CME::MDH::SecurityListener) are raised for security </div><div class="line"><a name="l00031"></a><span class="lineno"> 31</span>&#160;A only.</div><div class="line"><a name="l00032"></a><span class="lineno"> 32</span>&#160;</div><div class="line"><a name="l00033"></a><span class="lineno"> 33</span>&#160;If two or more securities are selected, events are triggered only for those securities.</div><div class="line"><a name="l00034"></a><span class="lineno"> 34</span>&#160;</div><div class="line"><a name="l00035"></a><span class="lineno"> 35</span>&#160;\see \ref security-selection</div><div class="line"><a name="l00036"></a><span class="lineno"> 36</span>&#160;</div><div class="line"><a name="l00037"></a><span class="lineno"> 37</span>&#160;[Permanent link to the answer](@ref faq-filtering)</div><div class="line"><a name="l00038"></a><span class="lineno"> 38</span>&#160;</div><div class="line"><a name="l00039"></a><span class="lineno"> 39</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00040"></a><span class="lineno"> 40</span>&#160;</div><div class="line"><a name="l00041"></a><span class="lineno"> 41</span>&#160;\section faq-book-consistency How do we know whether the data delivered through onBookAtomicUpdate is the first or last change of a &quot;transaction&quot;? That is, how can it be determined that the order book is valid/consistent/not-crossed after a single onBookAtomicUpdate() call?</div><div class="line"><a name="l00042"></a><span class="lineno"> 42</span>&#160;</div><div class="line"><a name="l00043"></a><span class="lineno"> 43</span>&#160;It is a bit more complicated with book consistency &amp; up-to-date. Please, note </div><div class="line"><a name="l00044"></a><span class="lineno"> 44</span>&#160;that CME does not guarantee 100% book up-to-date on intermediate updates.</div><div class="line"><a name="l00045"></a><span class="lineno"> 45</span>&#160;It is guaranteed only after &#39;End of XXX quote&#39; market event where XXX is real or </div><div class="line"><a name="l00046"></a><span class="lineno"> 46</span>&#160;implied. So you have to check this field to ensure the book is 100% up-to-date.</div><div class="line"><a name="l00047"></a><span class="lineno"> 47</span>&#160;</div><div class="line"><a name="l00048"></a><span class="lineno"> 48</span>&#160;It can be achieved by using book update callbacks of </div><div class="line"><a name="l00049"></a><span class="lineno"> 49</span>&#160;OnixS::CME::MDH::SecurityListener rather than atomic book update </div><div class="line"><a name="l00050"></a><span class="lineno"> 50</span>&#160;listening. They are publishing the books only on &#39;End of XXX quotes&#39; </div><div class="line"><a name="l00051"></a><span class="lineno"> 51</span>&#160;market event giving guarantee books are consistent and up-to-date.</div><div class="line"><a name="l00052"></a><span class="lineno"> 52</span>&#160;</div><div class="line"><a name="l00053"></a><span class="lineno"> 53</span>&#160;\see OnixS::CME::MDH::SecurityListener, OnixS::CME::MDH::MarketDataListener</div><div class="line"><a name="l00054"></a><span class="lineno"> 54</span>&#160;</div><div class="line"><a name="l00055"></a><span class="lineno"> 55</span>&#160;[Permanent link to the answer](@ref faq-book-consistency)</div><div class="line"><a name="l00056"></a><span class="lineno"> 56</span>&#160;</div><div class="line"><a name="l00057"></a><span class="lineno"> 57</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00058"></a><span class="lineno"> 58</span>&#160;</div><div class="line"><a name="l00059"></a><span class="lineno"> 59</span>&#160;\section faq-initial-book How to retrieve/receive the initial order book?</div><div class="line"><a name="l00060"></a><span class="lineno"> 60</span>&#160;</div><div class="line"><a name="l00061"></a><span class="lineno"> 61</span>&#160;Any OnixS::CME::MDH::SecurityListener::onBookUpdate call gives you </div><div class="line"><a name="l00062"></a><span class="lineno"> 62</span>&#160;consistent order book state (except for Natural Refresh mode). If you </div><div class="line"><a name="l00063"></a><span class="lineno"> 63</span>&#160;need book state at startup, you can just get a snapshot at first call.</div><div class="line"><a name="l00064"></a><span class="lineno"> 64</span>&#160;</div><div class="line"><a name="l00065"></a><span class="lineno"> 65</span>&#160;\see \ref book-construction-and-copying</div><div class="line"><a name="l00066"></a><span class="lineno"> 66</span>&#160;</div><div class="line"><a name="l00067"></a><span class="lineno"> 67</span>&#160;[Permanent link to the answer](@ref faq-initial-book)</div><div class="line"><a name="l00068"></a><span class="lineno"> 68</span>&#160;</div><div class="line"><a name="l00069"></a><span class="lineno"> 69</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00070"></a><span class="lineno"> 70</span>&#160;</div><div class="line"><a name="l00071"></a><span class="lineno"> 71</span>&#160;\section faq-no-market-data After switching the Operating System, even the sample program is no longer able to receive market data (code=NoNetworkActivity). However, I can ping the CME router and iLink server. Any insight or suggestions on what may be going on here?</div><div class="line"><a name="l00072"></a><span class="lineno"> 72</span>&#160;</div><div class="line"><a name="l00073"></a><span class="lineno"> 73</span>&#160;See \ref connectivity-troubleshooting.</div><div class="line"><a name="l00074"></a><span class="lineno"> 74</span>&#160;</div><div class="line"><a name="l00075"></a><span class="lineno"> 75</span>&#160;[Permanent link to the answer](@ref faq-no-market-data)</div><div class="line"><a name="l00076"></a><span class="lineno"> 76</span>&#160;</div><div class="line"><a name="l00077"></a><span class="lineno"> 77</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00078"></a><span class="lineno"> 78</span>&#160;</div><div class="line"><a name="l00079"></a><span class="lineno"> 79</span>&#160;\section faq-cache-limit-exceeded If Handler joins while the market is busy, warnings (code=QueueOverflow) are reported. Is there any possibility to raise the configured limit, if so how?</div><div class="line"><a name="l00080"></a><span class="lineno"> 80</span>&#160;</div><div class="line"><a name="l00081"></a><span class="lineno"> 81</span>&#160;When the Handler performs book recovery, it caches all the data received on incremental </div><div class="line"><a name="l00082"></a><span class="lineno"> 82</span>&#160;feeds. When the market is busy, a number of cached messages may exceed configured limit </div><div class="line"><a name="l00083"></a><span class="lineno"> 83</span>&#160;defined by the OnixS::CME::MDH::HandlerSettings::recoveryQueueMaxSize parameter value. </div><div class="line"><a name="l00084"></a><span class="lineno"> 84</span>&#160;So, to avoid `QueueOverflow` warnings, it is necessary to increase the value of the noted </div><div class="line"><a name="l00085"></a><span class="lineno"> 85</span>&#160;parameter.</div><div class="line"><a name="l00086"></a><span class="lineno"> 86</span>&#160;</div><div class="line"><a name="l00087"></a><span class="lineno"> 87</span>&#160;[Permanent link to the answer](@ref faq-cache-limit-exceeded)</div><div class="line"><a name="l00088"></a><span class="lineno"> 88</span>&#160;</div><div class="line"><a name="l00089"></a><span class="lineno"> 89</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00090"></a><span class="lineno"> 90</span>&#160;</div><div class="line"><a name="l00091"></a><span class="lineno"> 91</span>&#160;\section faq-queue-overflow What is the cause of &#39;QueueOverflow&#39; warnings?</div><div class="line"><a name="l00092"></a><span class="lineno"> 92</span>&#160;</div><div class="line"><a name="l00093"></a><span class="lineno"> 93</span>&#160;The cause is a violation of received packets sequence (gap) that wasn&#39;t restored </div><div class="line"><a name="l00094"></a><span class="lineno"> 94</span>&#160;after the OnixS::CME::MDH::RealtimeFeedSettings::outOfOrderPacketMaxInterval number </div><div class="line"><a name="l00095"></a><span class="lineno"> 95</span>&#160;of packets or after the OnixS::CME::MDH::HandlerSettings::lostPacketWaitTime elapsed. </div><div class="line"><a name="l00096"></a><span class="lineno"> 96</span>&#160;Violation of packet sequence can be caused by packets loss on different levels: </div><div class="line"><a name="l00097"></a><span class="lineno"> 97</span>&#160;CME environment issues, network connectivity issues, system or application issues.</div><div class="line"><a name="l00098"></a><span class="lineno"> 98</span>&#160;</div><div class="line"><a name="l00099"></a><span class="lineno"> 99</span>&#160;Also, when Handler performs a large-scale recovery due to the gap or while joining </div><div class="line"><a name="l00100"></a><span class="lineno"> 100</span>&#160;market lately, incremental packets are cached. In case of intensive data transmission,</div><div class="line"><a name="l00101"></a><span class="lineno"> 101</span>&#160;queue keeping incremental packets may reach its limit causing a noted warning. </div><div class="line"><a name="l00102"></a><span class="lineno"> 102</span>&#160;</div><div class="line"><a name="l00103"></a><span class="lineno"> 103</span>&#160;Please refer to our [Lost multicast packets troubleshooting guide](</div><div class="line"><a name="l00104"></a><span class="lineno"> 104</span>&#160;http://ref.onixs.biz/lost-multicast-packets-troubleshooting.html) </div><div class="line"><a name="l00105"></a><span class="lineno"> 105</span>&#160;for more details.</div><div class="line"><a name="l00106"></a><span class="lineno"> 106</span>&#160;</div><div class="line"><a name="l00107"></a><span class="lineno"> 107</span>&#160;\see \ref connectivity-troubleshooting.</div><div class="line"><a name="l00108"></a><span class="lineno"> 108</span>&#160;</div><div class="line"><a name="l00109"></a><span class="lineno"> 109</span>&#160;[Permanent link to the answer](@ref faq-queue-overflow)</div><div class="line"><a name="l00110"></a><span class="lineno"> 110</span>&#160;</div><div class="line"><a name="l00111"></a><span class="lineno"> 111</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00112"></a><span class="lineno"> 112</span>&#160;</div><div class="line"><a name="l00113"></a><span class="lineno"> 113</span>&#160;\section faq-book-atomic-and-complex-update What&#39;s the difference between &#39;Book Atomic Update&#39; and &#39;Book Update&#39; events?</div><div class="line"><a name="l00114"></a><span class="lineno"> 114</span>&#160;</div><div class="line"><a name="l00115"></a><span class="lineno"> 115</span>&#160;**Book Atomic Update** (OnixS::CME::MDH::SecurityListener::onBookAtomicUpdate) </div><div class="line"><a name="l00116"></a><span class="lineno"> 116</span>&#160;is an *elementary action over a book,* and usually, *there&#39;re multiple atomic </div><div class="line"><a name="l00117"></a><span class="lineno"> 117</span>&#160;updates inside a single snapshot or incremental refresh*. Also, the book *may not </div><div class="line"><a name="l00118"></a><span class="lineno"> 118</span>&#160;be valid between two atomic updates*. Only when all atomic updates are processed </div><div class="line"><a name="l00119"></a><span class="lineno"> 119</span>&#160;from the single market event, the book is considered as valid. </div><div class="line"><a name="l00120"></a><span class="lineno"> 120</span>&#160;</div><div class="line"><a name="l00121"></a><span class="lineno"> 121</span>&#160;**Book Update** (OnixS::CME::MDH::SecurityListener::onBookUpdate) are raised </div><div class="line"><a name="l00122"></a><span class="lineno"> 122</span>&#160;exactly at a time when all atomic updates are processed, and the book appears </div><div class="line"><a name="l00123"></a><span class="lineno"> 123</span>&#160;to be *valid* and *up-to-date*.</div><div class="line"><a name="l00124"></a><span class="lineno"> 124</span>&#160;</div><div class="line"><a name="l00125"></a><span class="lineno"> 125</span>&#160;\see \ref book-self-building</div><div class="line"><a name="l00126"></a><span class="lineno"> 126</span>&#160;</div><div class="line"><a name="l00127"></a><span class="lineno"> 127</span>&#160;[Permanent link to the answer](@ref faq-book-atomic-and-complex-update)</div><div class="line"><a name="l00128"></a><span class="lineno"> 128</span>&#160;</div><div class="line"><a name="l00129"></a><span class="lineno"> 129</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00130"></a><span class="lineno"> 130</span>&#160;</div><div class="line"><a name="l00131"></a><span class="lineno"> 131</span>&#160;\section faq-price-dividing While processing market data for CME, I noticed that some instruments are divided by 100, others by 10000 and the others are not. How do I determine what value to scale the prices?</div><div class="line"><a name="l00132"></a><span class="lineno"> 132</span>&#160;</div><div class="line"><a name="l00133"></a><span class="lineno"> 133</span>&#160;Security definition sent by Market Data Platform contains fields</div><div class="line"><a name="l00134"></a><span class="lineno"> 134</span>&#160;</div><div class="line"><a name="l00135"></a><span class="lineno"> 135</span>&#160;- DisplayFactor (tag 9787) - for securities with non-fractional price</div><div class="line"><a name="l00136"></a><span class="lineno"> 136</span>&#160;- MainFraction (tag 37702) and SubFraction (tag 37703) - for securities </div><div class="line"><a name="l00137"></a><span class="lineno"> 137</span>&#160; with fractional price</div><div class="line"><a name="l00138"></a><span class="lineno"> 138</span>&#160; </div><div class="line"><a name="l00139"></a><span class="lineno"> 139</span>&#160;representing the multipliers to convert the CME Globex display price to </div><div class="line"><a name="l00140"></a><span class="lineno"> 140</span>&#160;the conventional price.</div><div class="line"><a name="l00141"></a><span class="lineno"> 141</span>&#160;</div><div class="line"><a name="l00142"></a><span class="lineno"> 142</span>&#160;\see [CME Pricing documentaton](</div><div class="line"><a name="l00143"></a><span class="lineno"> 143</span>&#160;http://www.cmegroup.com/confluence/display/EPICSANDBOX/MDP+3.0+-+CME+Globex+Pricing).</div><div class="line"><a name="l00144"></a><span class="lineno"> 144</span>&#160;</div><div class="line"><a name="l00145"></a><span class="lineno"> 145</span>&#160;[Permanent link to the answer](@ref faq-price-dividing)</div><div class="line"><a name="l00146"></a><span class="lineno"> 146</span>&#160;</div><div class="line"><a name="l00147"></a><span class="lineno"> 147</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00148"></a><span class="lineno"> 148</span>&#160;</div><div class="line"><a name="l00149"></a><span class="lineno"> 149</span>&#160;\section faq-handler-latency Which latency is added by the Handler?</div><div class="line"><a name="l00150"></a><span class="lineno"> 150</span>&#160;</div><div class="line"><a name="l00151"></a><span class="lineno"> 151</span>&#160;Minimal book update latency falls into 100-250 nanoseconds depending </div><div class="line"><a name="l00152"></a><span class="lineno"> 152</span>&#160;on hardware/operating system/network conditions. Please, contact </div><div class="line"><a name="l00153"></a><span class="lineno"> 153</span>&#160;[Onix Sales](mailto:sales@onixs.biz) for most recent official </div><div class="line"><a name="l00154"></a><span class="lineno"> 154</span>&#160;benchmark results.</div><div class="line"><a name="l00155"></a><span class="lineno"> 155</span>&#160;</div><div class="line"><a name="l00156"></a><span class="lineno"> 156</span>&#160;[Permanent link to the answer](@ref faq-handler-latency)</div><div class="line"><a name="l00157"></a><span class="lineno"> 157</span>&#160;</div><div class="line"><a name="l00158"></a><span class="lineno"> 158</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00159"></a><span class="lineno"> 159</span>&#160;</div><div class="line"><a name="l00160"></a><span class="lineno"> 160</span>&#160;\section faq-handler-cpu-consumption What is Handler CPU consumption?</div><div class="line"><a name="l00161"></a><span class="lineno"> 161</span>&#160;</div><div class="line"><a name="l00162"></a><span class="lineno"> 162</span>&#160;It depends significantly on many different parameters including network,</div><div class="line"><a name="l00163"></a><span class="lineno"> 163</span>&#160;hardware, operating system environment, market data rate and applied </div><div class="line"><a name="l00164"></a><span class="lineno"> 164</span>&#160;handler settings.</div><div class="line"><a name="l00165"></a><span class="lineno"> 165</span>&#160;</div><div class="line"><a name="l00166"></a><span class="lineno"> 166</span>&#160;[Permanent link to the answer](@ref faq-handler-cpu-consumption)</div><div class="line"><a name="l00167"></a><span class="lineno"> 167</span>&#160;</div><div class="line"><a name="l00168"></a><span class="lineno"> 168</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00169"></a><span class="lineno"> 169</span>&#160;</div><div class="line"><a name="l00170"></a><span class="lineno"> 170</span>&#160;\section faq-expected-callback-latency What is the expected maximum latency our callback implementation should have?</div><div class="line"><a name="l00171"></a><span class="lineno"> 171</span>&#160;</div><div class="line"><a name="l00172"></a><span class="lineno"> 172</span>&#160;The smaller, the better. It shall be microseconds to do not </div><div class="line"><a name="l00173"></a><span class="lineno"> 173</span>&#160;impact handler ability to process data on high tickers.</div><div class="line"><a name="l00174"></a><span class="lineno"> 174</span>&#160;</div><div class="line"><a name="l00175"></a><span class="lineno"> 175</span>&#160;[Permanent link to the answer](@ref faq-expected-callback-latency)</div><div class="line"><a name="l00176"></a><span class="lineno"> 176</span>&#160;</div><div class="line"><a name="l00177"></a><span class="lineno"> 177</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00178"></a><span class="lineno"> 178</span>&#160;</div><div class="line"><a name="l00179"></a><span class="lineno"> 179</span>&#160;\section faq-error-reporting How are problems with market data indicated (book became invalid)?</div><div class="line"><a name="l00180"></a><span class="lineno"> 180</span>&#160;</div><div class="line"><a name="l00181"></a><span class="lineno"> 181</span>&#160;The Handler reports all errors and warnings </div><div class="line"><a name="l00182"></a><span class="lineno"> 182</span>&#160;through OnixS::CME::MDH::HandlerListener::onError and </div><div class="line"><a name="l00183"></a><span class="lineno"> 183</span>&#160;OnixS::CME::MDH::HandlerListener::onWarning callbacks </div><div class="line"><a name="l00184"></a><span class="lineno"> 184</span>&#160;respectively. </div><div class="line"><a name="l00185"></a><span class="lineno"> 185</span>&#160;</div><div class="line"><a name="l00186"></a><span class="lineno"> 186</span>&#160;\see \ref error-and-warning-handling</div><div class="line"><a name="l00187"></a><span class="lineno"> 187</span>&#160;</div><div class="line"><a name="l00188"></a><span class="lineno"> 188</span>&#160;[Permanent link to the answer](@ref faq-error-reporting)</div><div class="line"><a name="l00189"></a><span class="lineno"> 189</span>&#160;</div><div class="line"><a name="l00190"></a><span class="lineno"> 190</span>&#160;&lt;!--------------------------------------------------------------------------&gt;</div><div class="line"><a name="l00191"></a><span class="lineno"> 191</span>&#160;</div><div class="line"><a name="l00192"></a><span class="lineno"> 192</span>&#160;\section faq-detect-packet-issues How can packet issues (back-pressure/queuing) be diagnosed?</div><div class="line"><a name="l00193"></a><span class="lineno"> 193</span>&#160;</div><div class="line"><a name="l00194"></a><span class="lineno"> 194</span>&#160;The Handler allows tracing packets as they are received by active feeds </div><div class="line"><a name="l00195"></a><span class="lineno"> 195</span>&#160;including out-of-order or duplicated packets (in contrast to market </div><div class="line"><a name="l00196"></a><span class="lineno"> 196</span>&#160;data listening which exposes packets passed through session rules). </div><div class="line"><a name="l00197"></a><span class="lineno"> 197</span>&#160;With the help of the new OnixS::CME::MDH::FeedListener listener, it is </div><div class="line"><a name="l00198"></a><span class="lineno"> 198</span>&#160;possible to write advanced diagnostic services.</div><div class="line"><a name="l00199"></a><span class="lineno"> 199</span>&#160;</div><div class="line"><a name="l00200"></a><span class="lineno"> 200</span>&#160;\see \ref feed-event-listener</div><div class="line"><a name="l00201"></a><span class="lineno"> 201</span>&#160;</div><div class="line"><a name="l00202"></a><span class="lineno"> 202</span>&#160;[Permanent link to the answer](@ref faq-detect-packet-issues)</div></div><!-- fragment --></div><!-- contents -->
<!-- HTML footer for doxygen 1.8.11-->
<!-- start footer part -->
<footer>
<hr class="footer"/>
<address class="footer">
<small>&copy; <a href="http://www.onixs.biz">Onix Solutions [On<span class="corporate-orange">i</span>x<span class="corporate-orange">S</span>]</a>. All rights reserved.</small>
</address>
</footer>
</div> <!-- wrapper -->
</body>
</html>