简体   繁体   English

Mule HTTPS端点群集问题

[英]Mule HTTPS endpoint Cluster issue

We are facing one issue when we deploy our Mule application as war on Tomcat cluster on the same server. 当我们在同一服务器上的Tomcat群集上部署Mule应用程序作为战争时,我们面临一个问题。 It works fine when deployed on only one instance. 仅在一个实例上部署时,它可以正常工作。

We have one https connector defined in mule.config file as below, 我们在mule.config文件中定义了一个https连接器,如下所示,

<https:connector name="someConnector" ...doc:name="HTTP\HTTPS">
<reconnect frequency="5000" count="3"/>
<https:tls-key-store path="${keystr}" keyPassword="${pwd}" storePassword="${pwd}"/>
</https:connector>

Above connector is used to make a Http outbound connection to a url and in the endpoint we define port as 443, something like below, 上面的连接器用于建立与url的Http出站连接 ,在端点中,我们将端口定义为443,如下所示,

<https:outbound-endpoint exchange-pattern="request-response" password="xxx" user="xxx"    host="${abc}" path="${abc}" port="443" method="GET" connector-ref="someConnector" />            

Issue occurs when we deploy on Tomcat cluster, since the port is already used from one Tomcat instance, the application gives error on other instance. 当我们在Tomcat群集上进行部署时会发生问题,因为已经从一个Tomcat实例使用了端口,所以应用程序在另一个实例上给出了错误。 Below is the error, Root Exception stack trace: 下面是错误,根异常堆栈跟踪:

java.net.BindException: Address already in use
            at java.net.PlainSocketImpl.socketBind(Native Method)
            at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
            at java.net.ServerSocket.bind(ServerSocket.java:376)

Can you please suggest a way to resolve this issue ? 您能否提出解决此问题的方法?

Typically, that exception is associated with an inbound endpoint. 通常,该异常与入站终结点关联。 How are your inbound endpoints configured? 如何配置入站端点?

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM