WSO2 ESB代理服务的多个实例 [英] WSO2 ESB Multiple instances of proxy service

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

问题描述

我们正在使用WSO2 ESB,并且在传输方面,我们具有WebSphere MQ,可以使用JMS对其进行访问. 问题在于,每个代理服务都可以与WebSphere MQ在一个线程中一起工作,因此,我们遇到了性能问题. 我们如何在不部署代理服务的多个副本的情况下启动代理服务的多个实例?也许有一些隐藏的配置参数?

We are using WSO2 ESB and as transport we have WebSphere MQ which is accessed using JMS. Problem is that each proxy service works in one thread with WebSphere MQ and because of that we have performance issues. How can we start multiple instances of proxy service without deploying multiple copies of it? Maybe there are some hidden configuration parameters?

推荐答案

除了已经提到的参数

<parameter name="transport.jms.ConcurrentConsumers">2</parameter>

您可能需要添加另一个:

you might need to add another one:

<parameter name="transport.jms.IdleTaskLimit">2147483647</parameter>

此参数表示每个线程尝试读取空闲消息的次数.当此类空闲读取尝试的计数器等于该参数时,线程将停止读取消息(如果它不是唯一的读取器).

This parameter represents number of idle message read attempts per thread. When counter of such idle read attempts becomes equal to this parameter, the thread stops reading messages (if it is not the only reader).

鉴于此,将此参数设置为java int的上限将为您提供所有线程的几乎无限读取.

Given that, setting this parameter to the upper limit of java int provides you with virtually infinite reading by all the threads.

这篇关于WSO2 ESB代理服务的多个实例的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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