c# - 快速修复/n 错误 : MsgSeqNum too high-6ren

c# - 快速修复/n 错误 : MsgSeqNum too high

转载作者：行者123 更新时间：2023-12-03 21:40:27

我已经使用来自这个“http://www.quickfixn.org/download”的“QuickFIX/n is v1.4.0”创建了一个修复应用程序。 ' 地点。
当我执行一个应用程序时，我随机得到序列号错误。有时应用程序运行正常，有时我得到序列号问题。日志详细信息如下:

20130828-10:28:30.468 : Created session 

20130828-10:28:31.328 :> FIX.4.4:Server->Client Socket Reader 7995840 accepting session >FIX.4.4:Server->Client from 192.168.1.*:7356

20130828-10:28:31.328 :> FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:28:31.578 : Received logon 

20130828-10:28:31.625 :> Responding to logon request 

20130828-10:30:28.968 : Created session

20130828-10:30:29.796 : FIX.4.4:Server->Client Socket Reader 36610825 accepting session FIX.4.4:Server->Client from 192.168.1.*:7364

20130828-10:30:29.796 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:30.625 : Verify failed: MsgSeqNum too low,expecting 94 but received 44 

20130828-10:30:30.625 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 44 

20130828-10:30:31.375 :FIX.4.4:Server->Client Socket Reader 20554616 accepting session
 FIX.4.4:Server->Client from 192.168.1.*:7365 

20130828-10:30:31.375 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:31.468 : Verify failed: MsgSeqNum too low, expecting 94 but received 47 

20130828-10:30:31.468 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 47

20130828-10:30:32.406 : FIX.4.4:Server->Client Socket Reader 15510466 accepting session FIX.4.4:Server->Client from > 192.168.1.*:7366 

20130828-10:30:32.406 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:32.484 : Verify failed: MsgSeqNum too low, expecting 94 but received 49

20130828-10:30:32.484 : Session FIX.4.4:Server->Client disconnecting:Verify failed:MsgSeqNum too low, expecting 94 but received 49

20130828-10:30:33.390 : FIX.4.4:Server->Client Socket Reader 23324256
accepting session FIX.4.4:Server->Client from 192.168.1.*:7367

20130828-10:30:33.390 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:33.656 : Verify failed: MsgSeqNum too low,expecting 94 but received 51 

20130828-10:30:33.656 : SessionFIX.4.4:Server->Client disconnecting: Verify failed:MsgSeqNum too low, expecting 94 but received 51 

20130828-10:30:34.421 :FIX.4.4:Server->Client Socket Reader 34250480 accepting session FIX.4.4:Server->Client from 192.168.1.*:7368 

20130828-10:30:34.421 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:34.515 : Verify failed: MsgSeqNum too low, expecting 94 but received 53 
20130828-10:30:34.515 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 53 

20130828-10:30:35.546 : FIX.4.4:Server->Client Socket Reader 58408916 accepting session FIX.4.4:Server->Client from 192.168.1.*:7369 

20130828-10:30:35.546 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:35.625 : Verify failed: MsgSeqNum too low, expecting 94 but received 55

20130828-10:30:35.625 : Session FIX.4.4:Server->Client disconnecting:Verify failed: MsgSeqNum too low, expecting 94 but received 55

20130828-10:30:36.640 : FIX.4.4:Server->Client Socket Reader 2348279 accepting session FIX.4.4:Server->Client from 192.168.1.*:7370

20130828-10:30:36.640 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:36.734 : Verify failed: MsgSeqNum too low,expecting 94 but received 57 

20130828-10:30:36.734 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 57 

20130828-10:30:37.500 :FIX.4.4:Server->Client Socket Reader 61669314 accepting session
 FIX.4.4:Server->Client from 192.168.1.*:7371 

20130828-10:30:37.500 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:37.609 : Verify failed: MsgSeqNum too low, expecting 94 but received 59 

20130828-10:30:37.609 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 59 

20130828-10:30:38.531 : FIX.4.4:Server->Client Socket Reader 36865354 accepting session FIX.4.4:Server->Client from 192.168.1.*:7372 

20130828-10:30:38.531 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:38.640 : Verify failed: MsgSeqNum too low, expecting 94 but received 61

20130828-10:30:38.640 : Session FIX.4.4:Server->Client disconnecting:Verify failed: MsgSeqNum too low, expecting 94 but received 61

20130828-10:30:39.515 : FIX.4.4:Server->Client Socket Reader 3196068 accepting session FIX.4.4:Server->Client from 192.168.1.*:7373

20130828-10:30:39.515 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:39.781 : Verify failed: MsgSeqNum too low,expecting 94 but received 63 

20130828-10:30:39.781 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 63 

20130828-10:30:40.625 :FIX.4.4:Server->Client Socket Reader 4186222 accepting session
FIX.4.4:Server->Client from 192.168.1.*:7374 

20130828-10:30:40.625 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:40.718 : Verify failed: MsgSeqNum too low, expecting 94 but received 65 

20130828-10:30:40.718 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 65 

20130828-10:30:41.515 : FIX.4.4:Server->Client Socket Reader 764807 accepting session FIX.4.4:Server->Client from 192.168.1.*:7375 

20130828-10:30:41.515 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:41.796 : Verify failed: MsgSeqNum too low, expecting 94 but received 67

20130828-10:30:41.796 : Session FIX.4.4:Server->Client disconnecting:Verify failed: MsgSeqNum too low, expecting 94 but received 67

20130828-10:30:42.546 : FIX.4.4:Server->Client Socket Reader 10479095 accepting session FIX.4.4:Server->Client from 192.168.1.*:7376

20130828-10:30:42.546 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:42.640 : Verify failed: MsgSeqNum too low,expecting 94 but received 69 

20130828-10:30:42.640 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 69 

20130828-10:30:43.515 :FIX.4.4:Server->Client Socket Reader 4684807 accepting session
FIX.4.4:Server->Client from 192.168.1.*:7377 

20130828-10:30:43.515 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:43.750 : Verify failed: MsgSeqNum too low, expecting 94 but received 71 
20130828-10:30:43.750 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 71 

20130828-10:30:44.562 : FIX.4.4:Server->Client SocketReader 41662089 accepting session FIX.4.4:Server->Client from 192.168.1.*:7378 

20130828-10:30:44.562 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:44.656 : Verify failed: MsgSeqNum too low, expecting 94 but received 73

20130828-10:30:44.656 : Session FIX.4.4:Server->Client disconnecting:Verify failed: MsgSeqNum too low, expecting 94 but received 73

20130828-10:30:45.687 : FIX.4.4:Server->Client Socket Reader 46338128 accepting session FIX.4.4:Server->Client from 192.168.1.*:7379

20130828-10:30:45.687 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:45.812 : Verify failed: MsgSeqNum too low,expecting 94 but received 75 

20130828-10:30:45.812 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum toolow, expecting 94 but received 75 

20130828-10:30:46.593 :FIX.4.4:Server->Client Socket Reader 28975576 accepting session
 FIX.4.4:Server->Client from 192.168.1.*:7380 

20130828-10:30:46.593 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:46.656 : Verify failed: MsgSeqNum too low, expecting 94 but received 77 
20130828-10:30:46.656 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 77 

20130828-10:30:47.859 : FIX.4.4:Server->Client Socket Reader 11942173 accepting session FIX.4.4:Server->Client from 192.168.1.*:7381 

20130828-10:30:47.859 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:47.953 : Verify failed: MsgSeqNum too low, expecting 94 but received 79

20130828-10:30:47.953 : Session FIX.4.4:Server->Client disconnecting:Verify failed: MsgSeqNum too low, expecting 94 but received 79

20130828-10:30:48.593 : FIX.4.4:Server->Client Socket Reader 40054951 accepting session FIX.4.4:Server->Client from 192.168.1.*:7382

20130828-10:30:48.593 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 20130828-10:30:48.703 : Verify failed: MsgSeqNum too low,expecting 94 but received 81 

20130828-10:30:48.703 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum toolow, expecting 94 but received 81 

20130828-10:30:49.734 :FIX.4.4:Server->Client Socket Reader 9985467 accepting session FIX.4.4:Server->Client from 192.168.1.*:7383 

20130828-10:30:49.734 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:49.937 : Verify failed: MsgSeqNum too low, expecting 94 but received 83 

20130828-10:30:49.937 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 83 

20130828-10:30:50.703 : FIX.4.4:Server->Client Socket Reader 19425995 accepting session FIX.4.4:Server->Client from 192.168.1.*:7384 

20130828-10:30:50.703 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:51.062 : Verify failed: MsgSeqNum too low, expecting 94 but received 85

20130828-10:30:51.062 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 85

20130828-10:30:51.687 : FIX.4.4:Server->Client Socket Reader 34478086 accepting session FIX.4.4:Server->Client from 192.168.1.*:7385

20130828-10:30:51.687 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:51.781 : Verify failed: MsgSeqNum too low,expecting 94 but received 87 

20130828-10:30:51.781 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 87 

20130828-10:30:52.765 :FIX.4.4:Server->Client Socket Reader 42506536 accepting session
FIX.4.4:Server->Client from 192.168.1.*:7386 

20130828-10:30:52.765 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:52.859 : Verify failed: MsgSeqNum too low, expecting 94 but received 89 

20130828-10:30:52.859 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 89 

20130828-10:30:53.906 : FIX.4.4:Server->Client Socket Reader 26676330 accepting session FIX.4.4:Server->Client from 192.168.1.*:7387 

20130828-10:30:53.906 : FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds 

20130828-10:30:53.984 : Verify failed: MsgSeqNum too low, expecting 94 but received 91

20130828-10:30:53.984 : Session FIX.4.4:Server->Client disconnecting:Verify failed: MsgSeqNum too low, expecting 94 but received 91

20130828-10:30:54.796 : FIX.4.4:Server->Client Socket Reader 13812657 accepting session FIX.4.4:Server->Client from 192.168.1.*:7388

20130828-10:30:54.796 : FIX.4.4:Server->Client Acceptor heartbeat setto 0 seconds 

20130828-10:30:54.859 : Verify failed: MsgSeqNum too low,expecting 94 but received 93 

20130828-10:30:54.859 : Session FIX.4.4:Server->Client disconnecting: Verify failed: MsgSeqNum too low, expecting 94 but received 93 

20130828-10:30:55.812 :FIX.4.4:Server->Client Socket Reader 61488610 accepting session FIX.4.4:Server->Client from 192.168.1.*:7389 

20130828-10:30:55.812 :FIX.4.4:Server->Client Acceptor heartbeat set to 0 seconds

20130828-10:30:55.812 : Received logon 

20130828-10:30:55.843 :Responding to logon request 

20130828-10:30:55.843 : MsgSeqNum too high, expecting 94 but received 95 

20130828-10:30:55.843 : Sent ResendRequest FROM: 94 TO: 0 

20130828-10:30:55.875 : Got resend request from 49 to 0 

20130828-10:30:55.906 : Sent SequenceReset TO: 91 

20130828-10:30:55.906 : ResendRequest for messages FROM: 94 TO: 0 has been satisfied. 

20130828-10:30:55.906 : Received SequenceReset FROM:94 TO: 97 

20130828-10:31:24.421 : Session FIX.4.4:Server->Client disconnecting: Socket exception (192.168.1.*:7389): An existing connection was forcibly closed by the remote host

当我在配置文件中保留以下设置时，它工作正常。设置如下:

ResetOnLogon=Y
ResetOnLogout=Y
ResetOnDisconnect=Y

我希望它适用于配置文件中的以下设置。设置如下:

ResetOnLogon=N
ResetOnLogout=N
ResetOnDisconnect=N

请向我发送建议和设置以正确运行此应用程序。

感谢和注意，
维什韦什·拉瓦尔。

最佳答案

错误信息

MsgSeqNum too low, expecting XX but received YY

与您的客户端和远程服务器之间的策略有关。
一些服务器在每次登录时都需要重置，而其他服务器只需每天或每周一次。
如果您正在编写一个示例应用程序只是为了学习协议(protocol)，请尝试在您的配置文件中添加这一行:

ResetOnLogon=Y

但是，首先，尝试花一些时间来学习协议(protocol)。

关于c# - 快速修复/n 错误 : MsgSeqNum too high，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/18485976/

文章推荐： Maven 与 Cargo 和安装的 Glassfish

文章推荐： pdf - 在不破坏可访问性或 PDF 标签的情况下连接 PDF

文章推荐： android - Web SQL 和 SQLite 的区别

文章推荐： ios - 如何在iOS中以实际尺寸打印pdf

c - `#define LT(n) n, n, n, n, n, n, n, n, n, n, n, n, n, n, n, n`在这里做什么？
我看到以下宏 here . static const char LogTable256[256] = { #define LT(n) n, n, n, n, n, n, n, n, n, n, n,
ruby - 另一个与 "diff.*\n.*\n.*\n.*\n.*\n "相同的正则表达式
这个问题不太可能帮助任何 future 的访问者；它只与一个小的地理区域、一个特定的时间点或一个非常狭窄的情况有关，这些情况并不普遍适用于互联网的全局受众。为了帮助使这个问题更广泛地适用，visit
algorithm - n+n/2+n/3+...+n/n 之和的公式
所以我得到了这个算法我需要计算它的时间复杂度这样的 for i=1 to n do k=i while (k<=n) do FLIP(A[k]) k
algorithm - N 次幂 n i-e n^n 是否是多项式？ n^2 和 n^n 之间是否存在多项式差异？
n 的 n 次方(即 n^n)是多项式吗？ T(n) = 2T(n/2) + n^n 可以用master方法求解吗？最佳答案它不仅不是多项式，而且比阶乘还差。 O(n^n) 支配 O(n!)。同样
java - 从 Unicode 字符中删除变音符号 (ń ǹ ň ñ ṅ ņ ṇ ṋ ṉ ̈ ɲ ƞ ᶇ ɳ ȵ)
我正在研究一种算法，它可以在带有变音符号的字符(tilde、circumflex、caret、umlaut、caron)及其“简单”字符之间进行映射。例如: ń ǹ ň ñ ṅ ņ ṇ
fibonacci - 如何使用运算符(或其他东西)编写 N N N .... N？
嗯..我从昨天开始学习APL。我正在观看 YouTube 视频，从基础开始学习各种符号，我正在使用 NARS2000。我想要的是打印斐波那契数列。我知道有好几种代码，但是因为我没有研究过高深的东西，
math - 求解递推关系 T(n) = √n T(√n) + n
已关闭。这个问题是 off-topic 。目前不接受答案。想要改进这个问题吗？ Update the question所以它是on-topic用于堆栈溢出。已关闭12 年前。 Improve th
python - 从 N*N*N 到 N 的双射函数
谁能帮我从 N * N * N → N 中找到一个双射数学函数，它接受三个参数 x、y 和 z 并返回数字 n？我想知道函数 f 及其反函数 f'，如果我有 n，我将能够通过应用 f'(n) 来
regex - 如何在同一等式中搜索/替换所有 "n("-> "n*("和 ")n"-> ")*n"？
场景: 用户可以在字符串格式的方程式中输入任意数量的括号对。但是，我需要检查以确保所有括号 ( 或 ) 都有一个相邻的乘数符号 *。因此 3( 应该是 3*( 和 )3 应该是 )*3。我需要将所有
java - 为什么 n+++n 有效而 n++++n 无效？
在 Java 中，表达式: n+++n 似乎评估为等同于: n++ + n 尽管 +n 是一个有效的一元运算符，其优先级高于 n + n 中的算术 + 运算符。因此编译器似乎假设运算符不能是一元运算符
c - n = 0 和 n = n - n 之间的区别
当我阅读 this 问题我记得有人曾经告诉我(很多年前)，从汇编程序的角度来看，这两个操作非常不同: n = 0; n = n - n; 这是真的吗？如果是，为什么会这样？编辑: 正如一些回复所指出
javascript - ^\n\n\n 的含义
我正在尝试在reveal.js 中加载外部markdown 文件，该文件已编写为遵守数据分隔符语法: You can write your content as a separate file and
javascript - 使用 JavaScript，如何按照这些参数/规则生成随机 11 个字符字符串？ (L,L,L,L/N,L/N,N,N,N,N,N,N)
我试图弄清楚如何使用 Javascript 生成一个随机 11 个字符串，该字符串需要特定的字母/数字序列，以及位置。 ----------------------------------------
algorithm - 使用主方法求解 T(n) = 2T(n/2) + n/log n 和 T(n) = 4T(n/2) + n/log n 之间的区别
我最近偶然发现了一个资源，其中 2T(n/2) + n/log n 类型的递归被 MM 宣布为无法解决。直到今天，当另一种资源被证明是矛盾的(在某种意义上)时，我才接受它作为引理。根据资源(下面
python - 用十进制数 64165 位的 `n ** n` 计算 `n`(n 乘以 n)需要多长时间？
关闭。此题需要details or clarity 。目前不接受答案。想要改进这个问题吗？通过 editing this post 添加详细信息并澄清问题. 已关闭 8 年前。 Improve th
algorithm - O(n) + O(n log n) 是否等于 O(n log n)？
我完成的一个代码遵循这个模式: for (i = 0; i < N; i++){ // O(N) //do some processing... } sort(array, array + N
algorithm - 是否有可能证明 f(n) + g(n) = theta(n^2) for f(n) = theta(n^2) & g(n) = O(n^2)
有没有办法证明 f(n) + g(n) = theta(n^2) 还是不可能？假设 f(n) = theta(n^2) & g(n) = O(n^2) 我尝试了以下方法:f(n) = O(n^2) &
python - 仅当另一个 n*n 的值具有特定值时才显示 n*n 矩阵的值 (Python)
所以我目前正在尝试计算我拥有的一些数据的 Pearson R 和 p 值。这是通过以下代码完成的: import numpy as np from scipy.stats import pearson
postgresql - 如何从 n.n.n.n 格式的 ltree 中选择并在每个级别按数字排序？
ltree 列的默认排序为文本。示例:我的表 id、parentid 和 wbs 中有 3 列。 ltree 列 - wbs 将 1.1.12, 1.1.1, 1.1.2 存储在不同的行中。按 wbs
python - 为什么 while(n) n = n>>1 循环不以负数 n 终止
我的目标是编写一个程序来计算在 python 中表示数字所需的位数，如果我选择 number = -1 或任何负数，程序不会终止，这是我的代码: number = -1 cnt = 0 while(n

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

c# - 快速修复/n 错误 : MsgSeqNum too high