Wildfly 18 JMS执行导致“远程连接突然关闭”

如何解决Wildfly 18 JMS执行导致“远程连接突然关闭”

我有两个Wildfly 18实例在本地运行：n1和n2。我希望实例n2使用实例n1产生的消息，以便针对高可用性方案采取步骤。 阅读RH EAP docs之后， 我已经做了以下事情：

1-在n2上定义了一个公开的JMS队列。另外，我在ActiveMQ子模块中添加了安全设置和远程工厂：

[...]
<server name="default">
   <security-setting name="#">
       <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
   </security-setting>
[...]
   <jms-queue name="testQueue" entries="queue/test java:jboss/exported/jms/queue/test"/>
   <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
</server>
[...]

2-为了实现集群发现，我通过TCPPING配置了JGroups并加入了加入集群的初始节点列表：

[...]
<protocol type="org.jgroups.protocols.TCPPING">
   <property name="initial_hosts">127.0.0.1[8600]</property>
     <property name="port_range">0</property>
 </protocol>
[...]

3-然后我调出了两个实例，在那里我在应用程序日志中收到以下消息：

(Thread-12 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@7124120f)) AMQ221027: Bridge ClusterConnectionBridge@c6997b5 [name=$.artemis.internal.sf.my-cluster.f3561996-f354-11ea-83cc-4c32759d60cf,queue=QueueImpl[name=$.artemis.internal.sf.my-cluster.f3561996-f354-11ea-83cc-4c32759d60cf,postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=c9af42f1-f354-11ea-8e25-4c32759d60cf],temp=false]@2747e684 targetConnector=ServerLocatorImpl (identity=(Cluster-connection-bridge::ClusterConnectionBridge@c6997b5 [name=$.artemis.internal.sf.my-cluster.f3561996-f354-11ea-83cc-4c32759d60cf,temp=false]@2747e684 targetConnector=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector,factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=<port_number>&host=localhost],discoveryGroupConfiguration=null]]::ClusterConnectionImpl@1775690639[nodeUUID=c9af42f1-f354-11ea-8e25-4c32759d60cf,connector=TransportConfiguration(name=http-connector,factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=8323&host=localhost,address=jms,server=ActiveMQServerImpl::serverUUID=c9af42f1-f354-11ea-8e25-4c32759d60cf])) [initialConnectors=[TransportConfiguration(name=http-connector,discoveryGroupConfiguration=null]] is connected

但是当我尝试使用以下JNDI conf从n1到n2发送消息时，

java.naming.factory.initial = org.wildfly.naming.client.WildFlyInitialContextFactory
java.naming.provider.url = remote://localhost:8323
java.naming.security.principal = ***
java.naming.security.credentials = ***
Connection Factory JNDI name = jms/RemoteConnectionFactory
Queue JNDI name = jms/queue/test

...我在某个超时时间（约30秒）后收到此错误：

javax.naming.CommunicationException: WFNAM00018: Failed to connect to remote host [Root exception is java.io.IOException: JBREM000202: Abrupt close on Remoting connection 4ba0f2c1 to localhost/127.0.0.1:8323 of endpoint (anonymous)

我尝试使用一个简单的JMS客户端（https://plugins.jetbrains.com/plugin/10949-jms-messenger）连接到相同的队列，并且实际上能够连接，因为至少出现以下错误：

ERROR [com.my.app.Receiver] (Thread-14 (ActiveMQ-client-global-threads)) Unknown message: ActiveMQMessage[ID:5f71e993-f377-11ea-acfc-169f02eb582c]:PERSISTENT/ClientMessageImpl[messageID=442,durable=true,address=jms.queue.test,userID=5f71e993-f377-11ea-acfc-169f02eb582c,properties=TypedProperties[__AMQ_CID=5f684ca0-f377-11ea-acfc-169f02eb582c,_AMQ_ROUTING_TYPE=1]]

能否请您提示我什么地方不对，并解释为什么会这样？非常感谢

解决方法

我通过处理Wildfly和JNDI配置解决了此问题。尽管错误消息非常笼统，但至少就我而言，以下Wildfly配置：

<subsystem xmlns="urn:jboss:domain:messaging-activemq:8.0">
  <server name="default">
     <http-acceptor name="http-acceptor-throughput" http-listener="messaging">
                <param name="batch-delay" value="50"/>
                <param name="direct-deliver" value="false"/>
            </http-acceptor>
     ...
     <http-connector name="http-connector-throughput" socket-binding="messaging-throughput" endpoint="http-acceptor-throughput">
                <param name="batch-delay" value="50"/>
            </http-connector>
    ...
    <jms-queue name="test" entries="queue/test java:jboss/exported/jms/test"/>
    <broadcast-group name="bg-group1" jgroups-cluster="activemq-cluster" broadcast-period="5000" connectors="http-connector"/>
    <discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>        
    ...
    <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/> 
</subsystem>
...
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
   <http-connector name="messaging-remoting-connector" connector-ref="messaging-http" security-realm="ApplicationRealm"/>
</subsystem>
...
<socket-binding-group ... >
   ...
   <socket-binding name="messaging" port="8323"/>
   <socket-binding name="messaging-throughput" port="8324"/>
   ...
</socket-binding-group>

使用以下JNDI配置：

java.naming.factory.initial = org.wildfly.naming.client.WildFlyInitialContextFactory
java.naming.provider.url = remote://localhost:8323
java.naming.security.principal = ***
java.naming.security.credentials = ***
Connection Factory JNDI name = jms/RemoteConnectionFactory
Queue JNDI name = jms/test

此外，由于主体/凭证不是ApplicationRealm的一部分，因此我开始获得403 HTTP响应代码（在调用消息传递终结点时）。为了也能正常工作，我必须使用add-user.sh脚本（位于Wildfly /bin文件夹中）添加用户和相关凭证。