僵尸消息 [英] zombie messages

问题描述

我有singelton模式来批量组装消息。我在我的本地测试它，文件不是太大所以我保持10分钟的时间跨度。我收到18个edi记录的文件并试图处理它。我认为10分钟dealy足够好，因为
是非常小的消息。但是，当我运行测试时，所有消息都被暂停，并且 

I have singelton pattern to assemble messages in batch. I am testing it on my local and files are not too big so I keep timespan of 10 minutes. I am receiving file of 18 edi records and trying to process it. I think 10 minutes dealy is good enough as it is very small messages. But when I run a test all messages gows suspended with 

实例已完成而不会消耗其所有消息。该实例及其未使用的消息已被暂停。

The instance completed without consuming all of its messages. The instance and its unconsumed messages have been suspended.

让我知道如何避免它？ 

let me know how I can avoid it? 

推荐答案

最初，当我处理2条记录时，我有30秒的延迟，现在改为10分钟。我正在观察的一个蠢事。我放下文件的那一刻它就被暂停了。我希望看到运行服务实例10分钟。但我没有看到它。
我是否需要明确重置某些内容？看起来它仍然表现得像30秒延迟。

Initially I had this delay 30 seconds as I was working on 2 records , now change to 10 minutes. One starge thing I am observing. The moment I drop file it goes in suspended. i expect to see running service instance for 10 minutes. but I am not seeing it. Do I need to reset something explicitly? as looks like it still behave like 30 seconds delay.

我没有在我的singelton任何地方使用终止，我是否需要使用它作为强制性来避免这种行为？我不确定，但看起来很奇怪。

I am not using terminate in my singelton anywhere, do I need to use it as mandatory to avoid such behavior? I am not sure but looks very strange behavior .

这篇关于僵尸消息的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！