在Mule 3.4.X中是否仍可以将虚拟机队列配置为持久性? [英] Is it still possible to configure a vm queue as persistent in Mule 3.4.X?

问题描述

我正在尝试像这样配置vm连接器:

I am trying to configure a vm connector like so:

<vm:connector name="recordDeletedActivityDLQStore">
   <vm:queue-profile maxOutstandingMessages="500" >
     <file-queue-store/>
   </vm:queue-profile>
</vm:connector>

Mule Studio抱怨说这不是vm:queue-profile的允许子元素.这也不会生成和运行.我尝试了其他可能的输入来定义队列存储的性质，但没有任何运气.我找不到任何有关如何配置有效的虚拟机队列的文档.具体来说，我尝试按照VM传输参考中所述，将属性persistent ="true"添加到queue-profile元素:

Mule Studio complains that is not a permitted child element of vm:queue-profile. This will not build and run either. I've tried other possible inputs for defining the nature of the queue store without any luck. I can't find any documentation on how to configure persistent vm queues that works. Specifically, I have tried adding the attribute persistent="true" to the queue-profile element as described in VM Transport Reference: http://www.mulesoft.org/documentation/display/34X/VM+Transport+Reference

似乎也不再受支持...

This doesn't seem to be supported anymore either...

在Mule 3.4.X中是否仍可以将虚拟机队列配置为持久性?

Is it still possible to configure a vm queue as persistent in Mule 3.4.X?

推荐答案

您的配置正确且有效:您可以看到消息保留在.mule/${app_name}/queuestore/${queue_name}/下的磁盘上.

Your configuration is correct and works: you can see that messages are persisted on disk under .mule/${app_name}/queuestore/${queue_name}/.

持久性仅在one-way个VM队列中发生，而在request-response个虚拟机队列中不发生.对于后者，不会发生任何排队.

Persistence only occurs for one-way VM queues, not request-response ones. For the latter, no queueing occurs whatsoever.

此外，请忽略Studio有关您的配置无效的投诉.关于配置有效性，Mule拥有最终决定权，您的确定就可以了.

Also, disregard Studio complaints about your configuration not being valid. Mule has the final word on configuration validity, and yours is just fine.

这篇关于在Mule 3.4.X中是否仍可以将虚拟机队列配置为持久性?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！