<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-IN" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hello All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Is Anyone using any mechanism to sync the message stores between active/passive setup?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">It would be a great help if anyone can assist further on this.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Sumit<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Quickfixn <quickfixn-bounces@lists.quickfixn.com>
<b>On Behalf Of </b>Sumit Gupta (SUGU)<br>
<b>Sent:</b> 02 October 2018 21:11<br>
<b>To:</b> Mailing list for QuickFIX/n <quickfixn@lists.quickfixn.com><br>
<b>Subject:</b> Re: {{Quickfixn}} Can be message store given a shared path<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Mike,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you for your quick reply.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As our service is critical and lot of fix traffic it handles. You can imagine that in 2.5 days one of the fix store (for a client) goes upto 3 gb.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I am not sure if shared path implementation will introduce latency to fix messages delivery. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Could you/anyone put some light here, if anyone is already using shared path for message store.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And also why RefreshOnLogon=y while reconnecting on passive to active server?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Sumit<o:p></o:p></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:5.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt">From: </span></b><span style="font-size:10.5pt">Mike Gatny <<a href="mailto:mgatny@connamara.com">mgatny@connamara.com</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt">Date: </span></b><span style="font-size:10.5pt">Tuesday, 02 Oct 2018, 7:53 PM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt">To: </span></b><span style="font-size:10.5pt">Mailing list for QuickFIX/n <<a href="mailto:quickfixn@lists.quickfixn.com">quickfixn@lists.quickfixn.com</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt">Subject: </span></b><span style="font-size:10.5pt">Re: {{Quickfixn}} Can be message store given a shared path<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Oct 2, 2018 at 9:52 AM Sumit Gupta (SUGU) <<a href="mailto:SUGU@saxobank.com">SUGU@saxobank.com</a>> wrote:<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal">I could see one resolution:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">1. If I mention the message store path as shared path. ( i am not sure if this is a practical resolution).<o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Yes, do this, and use RefreshOnLogon=Y. This setting causes the store files to be re-read when clients logon to the Passive.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Another solution is to use a datatbase-backed implementation of IMessageStore. QuickFIX/n does not currently include one, but you could implement one fairly easily.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">--</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Mike Gatny</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Connamara Systems</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p><span style="font-size:8.5pt">This email may contain confidential and/or privileged information. If you are not the intended recipient - or have received this email by mistake - please notify the sender immediately and destroy the email. Any unauthorised
copying, disclosure and/or distribution of the contents and/or attachments in this email is strictly prohibited.</span><o:p></o:p></p>
<p><span style="font-size:8.5pt">Email transmission security and error-free delivery cannot be guaranteed as information could be intercepted, corrupted, destroyed, delayed, incomplete and/or contain malware (virus). The sender of this email, therefore, does
not accept liability for any errors and/or omissions in the contents of this message, which may arise as a result of email transmission.</span><o:p></o:p></p>
</div>
<p><span style="font-size: 11px;">This email may contain confidential and/or privileged information. If you are not the intended recipient - or have received this email by mistake - please notify the sender immediately and destroy the email. Any unauthorised copying, disclosure and/or distribution of the contents and/or attachments in this email is strictly prohibited.</span></p><p><span style="font-size: 11px;">Email transmission security and error-free delivery cannot be guaranteed as information could be intercepted, corrupted, destroyed, delayed, incomplete and/or contain malware (virus). The sender of this email, therefore, does not accept liability for any errors and/or omissions in the contents of this message, which may arise as a result of email transmission.</span></p></body>
</html>