Xmpp ejabberd:未确认XML节

Xmpp ejabberd:未确认XML节,xmpp,ejabberd,stream-management,Xmpp,Ejabberd,Stream Management,在恢复ejabberd的流管理会话时,我得到以下日志: 2016-04-11 08:53:07.430 [info] <0.5432.11>@ejabberd_c2s:terminate:1752 Closing former stream of resumed session for 54ff31587261691606060000@108.59.83.204/sender 2016-04-11 08:53:07.430 [info] <0.7868.11>@ejabb

在恢复ejabberd的流管理会话时,我得到以下日志:

2016-04-11 08:53:07.430 [info] <0.5432.11>@ejabberd_c2s:terminate:1752 Closing former stream of resumed session for 54ff31587261691606060000@108.59.83.204/sender
2016-04-11 08:53:07.430 [info] <0.7868.11>@ejabberd_c2s:handle_unacked_stanzas:2814 1 stanzas were not acknowledged by 54ff31587261691606060000@108.59.83.204/sender
2016-04-11 08:53:07.430 [info] <0.7868.11>@ejabberd_c2s:handle_resume:2731 Resumed session for 54ff31587261691606060000@108.59.83.204/sender
2016-04-11 08:53:08.602 [info] <0.8227.11>@ejabberd_c2s:handle_enable:2644 Stream management with resumption enabled for 5695b87d7261697179130000@108.59.83.204/sender
2016-04-11 08:53:09.516 [info] <0.8227.11>@ejabberd_c2s:terminate:1779 ({socket_state,gen_tcp,#Port<0.138899>,<0.8244.11>}) Close session for 5695b87d7261697179130000@108.59.83.204/sender
2016-04-11 08:53:09.517 [info] <0.8227.11>@ejabberd_c2s:handle_unacked_stanzas:2814 1 stanzas were not acknowledged by 5695b87d7261697179130000@108.59.83.204/sender
2016-04-11 08:53:09.987 [info] <0.458.0>@ejabberd_listener:accept:333 (#Port<0.138210>) Accepted connection 106.196.172.221:58035 -> 10.240.0.3:5222
2016-04-11 08:53:11.157 [info] <0.8254.11>@ejabberd_c2s:wait_for_sasl_response:919 ({socket_state,gen_tcp,#Port<0.138210>,<0.8185.11>}) Accepted authentication for 5695b87d7261697179130000 by undefined from 106.196.172.221
2016-04-11 08:53:07.430[信息]@ejabberd_c2s:terminate:1752结束前一轮的恢复会议54ff31587261691606060000@108.59.83.204/寄件人
2016-04-11 08:53:07.430[信息]@ejabberd_c2s:handle_unacked_stanzas:2814 1节未被确认54ff31587261691606060000@108.59.83.204/寄件人
2016-04-11 08:53:07.430[信息]@ejabberd_c2s:handle_resume:2731会议续会54ff31587261691606060000@108.59.83.204/寄件人
2016-04-11 08:53:08.602[信息]@ejabberd_c2s:handle_enable:2644启用恢复的流管理5695b87d7261697179130000@108.59.83.204/寄件人
2016-04-11 08:53:09.516[信息]@ejabberd_c2s:terminate:1779({socket_state,gen_tcp,#Port,})的会话结束5695b87d7261697179130000@108.59.83.204/寄件人
2016-04-11 08:53:09.517[信息]@ejabberd_c2s:handle_unacked_stanzas:2814 1节未被确认5695b87d7261697179130000@108.59.83.204/寄件人
2016-04-11 08:53:09.987[信息]@ejabberd_侦听器:接受:333(#端口)接受的连接106.196.172.221:58035->10.240.0.3:5222
2016-04-11 08:53:11.157[信息]@ejabberd_c2s:wait_for_sasl_响应:919({socket_state,gen_tcp,#Port,})从106.196.172.221接受了未定义的5695b87d7261697179130000的身份验证
这里有一节未被承认,它是什么意思,以及如何纠正它

有时,接收方客户机没有收到很少的交付确认,这是这些节丢失的原因吗

更新: 会话期间未确认的节将在连接恢复时再次交换。但是有些情况下,某些节丢失了,因此发送确认不会反映在发送方客户端

为流管理设置的参数:

超时恢复:120秒

超时时重新发送:true


是否有任何配置可能会丢失,导致某些节丢失?

这意味着您正在使用流管理,并且您的客户没有确认他收到了某些节。如果这是邮件,它们将被存储以供脱机传递或在其他连接上重新发送,因此您不应丢失任何邮件