实例没有卸载 [英] instances not unloading

查看:97
本文介绍了实例没有卸载的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好我们有一个顺序工作流程,我们用它来控制我们做什么和什么时候做什么。我们将DelayActivities用于"when"时间。和CodeActivities包含对"what"的现有webservice方法的调用。通常情况下,一个实例持续大约10天,大多数是空闲,醒来4到5次做某事。它运行在一个盒子上并使用oob sql持久性。 OwnershipTimeoutSeconds = 0. UnloadOnIdle = true。从历史上看,实例会被加载,执行某些操作,进行空闲,持久化,卸载。内存使用量保持最低。但是,最近,运行时希望将所有实例保留在内存中。最近的变化*似乎都没有成为罪魁祸首。我很感激任何建议。



Mark

Hi
We have a sequential workflow which we use to control what things we do and when.  We use the DelayActivities for the "when" and CodeActivities wrapping calls to existing webservice methods for the "what".  Typically an instance lasts about 10 days, mostly idle, waking up 4 or 5 times to do something.  It is running on a single box and uses oob sql persistence.  OwnershipTimeoutSeconds = 0.  UnloadOnIdle = true.  Historically an instance gets loaded, does something, goes idle, gets persisted, gets unloaded.  Memory usage is kept to minumum.  Recently, though, the runtime wants to keep all instances in memory.  None of the recent changes *appear* to be the culprit.  I'd appreciate any suggestions.

Thanks
Mark

推荐答案

Hi Mark,

您的OwnerShipTimeOutDuration是否始终设置为零秒?这是工作流运行时保留所有权的时间。我们发现了一个有趣的"特征",即当所有权低于某个值时,实例仍然被锁定(即仍在使用中)。我会设置为1000秒,看看这是否能解决问题以及是否确实降低了值。

希望这会有所帮助。
Hi Mark,

Has your OwnerShipTimeOutDuration always been set to zero seconds?  This is how long the workflow runtime holds the ownership. We discovered an interesting 'feature' in that when the ownership was below a certain value the instances remained locked (i.e. still in use).  I would set to 1000 seconds to see if this resolves the problem and if it does lower the value.

Hope this helps.


这篇关于实例没有卸载的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆