快速修复/n 错误:MsgSeqNum 太高

2024-02-06

我已经使用“QuickFIX/n is v1.4.0”从此“创建了一个修复应用程序”http://www.quickfixn.org/download http://www.quickfixn.org/download' 地点。 当我执行应用程序时,我随机出现序列号错误。有时应用程序运行良好,有时出现序列号问题。日志详细信息如下:

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 太低,期望 XX 但收到 YY

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

ResetOnLogon=Y

但是,首先,尝试花一些时间来学习该协议。

本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)

快速修复/n 错误:MsgSeqNum 太高 的相关文章

随机推荐

  • HTTPS 和外部 (CDN) 托管文件?

    我有一个页面引用了几个外部托管的 javascript 文件 即 谷歌上的 jQuery http code google com apis libraries devguide html and YUI 使用 YUI 加载器 http d
  • 已编译的查询和“参数不能是序列”

    我认为编译的查询将执行与 DataContext 相同的查询转换 然而 当我尝试使用带有 Contains 方法调用的查询时 出现运行时错误 我哪里出错了 private member which holds a compiled quer
  • 发送大量UDP数据包时如何减少系统调用开销? (Windows 和 Linux)

    例如 我在 Windows 上发送 100000 个 UDP 数据包 对于每个数据包 我需要调用WSASendTo 一次 所以可能会引入很多系统调用开销 有没有办法进行批量发送并减少这种开销 我在谷歌搜索了一段时间后找不到适用于 Windo
  • 如何在android中像没有微调器的微调器一样弹出列表?

    我的活动中有一个微调器小部件 可让用户选择列表名称 通常 微调器的功能是在列表之间切换 但对于几个实例 我交换了选择更改侦听器以使用相同的选项列表执行不同的功能 一旦做出选择 老听众就会恢复 生活继续 这是一个糟糕且有问题的安排 相反 我想
  • 使用 connect by 子句递归插入

    我在表中有分层数据 右 按照以下方式创建层次结构 如左所示 表保存在 oracle 11g 中 TREE Hierarchy Tree Table Element Parent P0 P0 P1 P1 P0 P11 P2 P0 C111 P
  • 在 C 中执行简单 MPI 程序时集群挂起/显示错误

    我正在尝试运行一个简单的 MPI 程序 多个数组加法 它在我的 PC 中完美运行 但只是挂起或在集群中显示以下错误 我正在使用 open mpi 和以下命令来执行 集群网络配置 主节点1 MASTER eth0 Link encap Eth
  • 如何在 VB.net 中让函数运行回调

    恐怕我一直在谷歌搜索这个 但找不到我理解或可以使用的答案 在 Javascript 中 您可以运行一个函数并设置一个回调函数 该函数在第一个函数运行后调用 function doThis callBack do things do thin
  • gulp 和 karma,文件 karma.conf.js 不存在

    我有一个基本的 AngularJS 应用程序 希望让我的所有终端命令都通过 gulp 任务运行 例如 gulp dev对于开发服务器和 gulp unitTest用于测试等 我已经按照文档安装了 Gulp npm install save
  • 将驱动器号转换为分区 ID/磁盘 ID

    给定驱动器盘符 我如何获得OSImage安装到分区ID http technet microsoft com en us library ff716430 aspx and Disk ID http technet microsoft co
  • BCC 发送 PHP mail() 到邮件列表的方式与 TO 不同吗?

    我正在改进 PHP 邮件列表代码 使用mail 在循环中迭代所有订阅者 该脚本用于显示 超出最大执行时间 30 秒 错误 我通过添加解决了该错误set time limit 0 现在没有错误 但发送 100 条消息花了大约七分钟 我有什么选
  • 如何了解System.Windows.Forms.dll中System.InvalidOperationException的详细信息?

    运行我的应用程序时 我在 Visual Studio 的 输出 面板中发现了下面的异常日志 System Windows Forms dll 中发生 System InvalidOperationException 类型的第一次机会异常 该
  • 动态像素化 html 图像元素

    我要在网页上拍摄图像 然后使用 javascript 或最适合的任何内容 对其进行动态 像素化 例如 变成 20px 的正方形 然后 当用户向下滚动页面时 我需要图像的分辨率逐渐增加 直到它不再像素化 我有什么想法可以去做这件事吗 我意识到
  • PayPal Express Checkout 集成响应

    我目前很难理解我的 PayPal EC 集成的响应 GetExpressCheckoutDetails 响应是 CHECKOUTSTATUS gt PaymentActionNotInitiated 但在 DoExpressCheckout
  • WPF设计问题(自定义控件或mvvm)

    这是场景 我有一个显示一些数据的视觉效果 The data to the visual can come in one of two ways 通过用户通过键盘或鼠标输入 通过一些后端源 Both these data inputs can
  • WooCommerce 上的购物车总重量和运输重新计算

    我正在尝试使用一个片段将我的自定义盒子重量添加到总订单重量中 目前工作正常 但是 不会根据重新计算的片段重量重新计算运输方式 有什么想法如何强制重新计算运费吗 add filter woocommerce cart contents wei
  • 完全删除 MySQL 5.7 [关闭]

    Closed 这个问题是无关 help closed questions 目前不接受答案 我正在尝试从 ubuntu 12 04 中完全卸载 mysql 但没能做到 我尝试了很多命令 但没有任何作用 任何人都可以帮忙吗 sudo apt g
  • 用于对基于时间的值进行排序的 Redis 数据结构设计

    我正在对数据流执行一些分析并将结果发布到 Redis 通道上 消费者订阅这些频道并获取实时数据源 所有历史数据分析结果都会丢失 现在我想添加在Redis中存储历史数据的能力 以便消费者可以查询这些历史数据 主要是按时间 由于分析结果按时间分
  • 如何在一项任务中执行多个 gulp 命令

    我很难理解如何在单个任务中处理多个 gulp 源 在这样的任务中 gulp task task1 function cb gulp src src js pipe gulp dest dist gulp src src css pipe g
  • 如何将 Linux shell 脚本编译为独立的可执行文件*二进制*(即不仅仅是 chmod 755)?

    我正在寻找一个免费的开源工具集 可以编译各种 经典 脚本语言 例如Korn Shell ksh csh bash 等作为可执行文件 如果脚本调用其他程序或可执行文件 则将它们包含在单个可执行文件中 Reasons 混淆交付给客户的代码 以免
  • 快速修复/n 错误:MsgSeqNum 太高

    我已经使用 QuickFIX n is v1 4 0 从此 创建了一个修复应用程序 http www quickfixn org download http www quickfixn org download 地点 当我执行应用程序时 我