堆栈内存溢出
  繁体   English   中英

无法从一个Wildfly 10应用连接到另一个JMS队列

[英]Trouble connecting to a remote JMS queue from one wildfly 10 app to another

 原文  2017-08-02 12:44:29  1   1    java/ jms/ wildfly-10/ message-driven-bean

问题描述

我有两个Wildfly 10服务器正在运行，并且有一个与Jboss和Hornet一起工作的JMS队列。 在那里，我使用netty连接器，因此我废弃了所有配置，并获得了wildfy 10上用于消息传递的默认配置。我无法使JMS正常工作。 我还没有真正找到能满足我需求的优秀文档或示例。 希望有人能帮忙。

服务器端

我已在服务器端将wildfly 10服务器设置为使用standalone-full.xml来获取消息传递扩展。

这是与消息传递有关的standalone-full.xml内容（默认情况下不添加任何内容） 

<extension module="org.wildfly.extension.messaging-activemq"/>

<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
        <server name="default">
            <security-setting name="#">
                <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
            </security-setting>
            <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
            <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="http"/>
            <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http">
                <param name="batch-delay" value="50"/>
            </http-connector>
            <in-vm-connector name="in-vm" server-id="0"/>
            <http-acceptor name="http-acceptor" http-listener="default"/>
            <http-acceptor name="http-acceptor-throughput" http-listener="default">
                <param name="batch-delay" value="50"/>
                <param name="direct-deliver" value="false"/>
            </http-acceptor>
            <in-vm-acceptor name="in-vm" server-id="0"/>
            <jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>
            <jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>
            <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
            <connection-factory name="RemoteConnectionFactory" entries="java:/jms/RemoteConnectionFactory" connectors="http-connector"/>
            <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
        </server>
    </subsystem>

这是我为定义队列和使用MessageDrivenBean接收消息而编写的代码： 

@MessageDriven(activationConfig = { 
  @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
  @ActivationConfigProperty(propertyName = "destination", propertyValue = "java:app/jms/queue/SecServerQ")
})
@JMSDestinationDefinition(
  name = "java:app/jms/queue/SecServerQ",
  interfaceName = "javax.jms.Queue",
  destinationName = "SecServerQ"
)
public class SecServerMDB implements MessageListener
{
  public void onMessage(Message message)
  {
    // my code here
  }
}

我可以在wildfly控制台中看到队列：

在此处输入图片说明

客户端

我有一个standalone-full.xml消息传递部分，它也与我的clientserver上的服务器端配置文件相同。

这是我用来尝试与服务器端JMS队列建立连接的代码。 

public class WildFlyJmsQueueSender
{
  private static final Logger log = LoggerFactory.getLogger(WildFlyJmsQueueSender.class);

  public final static String JMS_CONNECTION_FACTORY_JNDI="jms/RemoteConnectionFactory";
  public final static String JMS_QUEUE_JNDI="jms/queue/SecServerQ";
  public final static String JMS_USERNAME="jmsuser";       //  The role for this user is "guest" in ApplicationRealm
  public final static String JMS_PASSWORD="jms2017Pwd!";
  public final static String WILDFLY_REMOTING_URL="http-remoting://secserver.mydomain.com:8080";

  public void send(IpcoJmsMessage msg, String msgType) throws NamingException, JMSException {

    Context namingContext = null;

    try {
      namingContext = getInitialContext();

      log.debug("Attempting to acquire connection factory {}", JMS_CONNECTION_FACTORY_JNDI);
      ConnectionFactory conFactory = (ConnectionFactory) namingContext.lookup(JMS_CONNECTION_FACTORY_JNDI);
      log.debug("Found connection factory {} in JNDI", JMS_CONNECTION_FACTORY_JNDI);

      log.debug("Attempting to acquire destination {}", JMS_QUEUE_JNDI);
      Destination destination = (Destination) namingContext.lookup(JMS_QUEUE_JNDI);
      log.debug("Found destination {} in JNDI", JMS_QUEUE_JNDI);

      try (JMSContext context = conFactory.createContext(JMS_USERNAME, JMS_PASSWORD)) {
        ObjectMessage objMsg = context.createObjectMessage();
        objMsg.setObject(msg);
        objMsg.setStringProperty("msgType", msgType);

        log.info("Sending message with content msg={}, msgType={}", msg, msgType);

        context.createProducer().send(destination, objMsg);
      }
    } catch (NamingException e) {
      log.error("NamingException: {} {}", e.getMessage(), e);
    } finally {
      if(namingContext != null) {
        try {
          namingContext.close();
        } catch (NamingException e) {
          log.error(e.getMessage());
        }
      }
    }
  }

  private static InitialContext getInitialContext() throws NamingException {
    InitialContext context=null;
    try {
      Properties props = new Properties();
      props.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");
      props.put(Context.PROVIDER_URL, WILDFLY_REMOTING_URL);
      props.put(Context.SECURITY_PRINCIPAL, JMS_USERNAME);
      props.put(Context.SECURITY_CREDENTIALS, JMS_PASSWORD);
      context = new InitialContext(props);

      log.debug("Got initial Context: "+context);

    } catch (Exception e) {
      e.printStackTrace();
    }
    return context;
  }

}

这是我在客户端遇到的异常： 

14:11:04.965 DEBUG [LoggerProviders.java:158] - Logging Provider: org.jboss.logging.Slf4jLoggerProvider
14:11:04.966 INFO  [Version.java:61] - WildFly Naming version 1.0.0.Beta13
14:11:04.969 DEBUG [WildFlyJmsQueueSender.java:82] - Got initial Context: javax.naming.InitialContext@2c7d3911
14:11:04.969 DEBUG [WildFlyJmsQueueSender.java:42] - Attempting to acquire connection factory jms/RemoteConnectionFactory
14:11:05.033 INFO  [Xnio.java:95] - XNIO version 3.5.0.Beta2
14:11:05.043 INFO  [NioXnio.java:57] - XNIO NIO Implementation Version 3.5.0.Beta2
14:11:05.069 DEBUG [WorkerThread.java:433] - Started channel thread 'XNIO-1 Accept', selector sun.nio.ch.EPollSelectorImpl@2883da14
14:11:05.069 DEBUG [WorkerThread.java:433] - Started channel thread 'XNIO-1 I/O-1', selector sun.nio.ch.EPollSelectorImpl@338779b1
14:11:05.081 INFO  [EndpointImpl.java:97] - JBoss Remoting version 5.0.0.Beta19
14:11:05.087 DEBUG [WorkerThread.java:433] - Started channel thread 'Remoting (anonymous) I/O-1', selector sun.nio.ch.EPollSelectorImpl@5375fba8
14:11:05.087 DEBUG [WorkerThread.java:433] - Started channel thread 'Remoting (anonymous) Accept', selector sun.nio.ch.EPollSelectorImpl@331af02b
14:11:05.141 INFO  [Version.java:57] - ELY00001: WildFly Elytron version 1.1.0.Beta33
14:11:05.382 ERROR [WildFlyJmsQueueSender.java:60] - NamingException: {}WFNAM00018: Failed to connect to remote host
javax.naming.CommunicationException: WFNAM00018: Failed to connect to remote host
at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:65) ~[wildfly-naming-client-1.0.0.Beta13.jar:1.0.0.Beta13]
at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:109) ~[wildfly-naming-client-1.0.0.Beta13.jar:1.0.0.Beta13]
at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:99) ~[wildfly-naming-client-1.0.0.Beta13.jar:1.0.0.Beta13]
at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:108) ~[wildfly-naming-client-1.0.0.Beta13.jar:1.0.0.Beta13]
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:78) ~[wildfly-naming-client-1.0.0.Beta13.jar:1.0.0.Beta13]
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:64) ~[wildfly-naming-client-1.0.0.Beta13.jar:1.0.0.Beta13]
at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144) ~[wildfly-naming-client-1.0.0.Beta13.jar:1.0.0.Beta13]
at javax.naming.InitialContext.lookup(InitialContext.java:417) ~[na:1.8.0_121]
at javax.naming.InitialContext.lookup(InitialContext.java:417) ~[na:1.8.0_121]
at no.ipco.common.WildFlyJmsQueueSender.send(WildFlyJmsQueueSender.java:43) ~[ipco-common-jmsclient-0.1.jar:na]

1 个解决方案

解决方案1
 1  2017-08-02 14:41:02

我解决了问题。

首先，我在MessageDrivenBean服务器端使用@JMSDestinationDefinition。 相反，我使用jboss-cli定义了队列。

我的standalone-full.xml配置文件现在添加了以下行 

<jms-queue name="SecServerQ" entries="jms/queue/SecServerQ java:jboss/exported/jms/queue/SecServerQ"/>

在客户端，我切换了端口。 我尝试通过telnet到8080（旧端口），并且那里没有开放，所以我尝试使用28080。 将clientcode修改为： 

public final static String JMS_CONNECTION_FACTORY_JNDI="jms/RemoteConnectionFactory";
public final static String JMS_QUEUE_JNDI="jms/queue/SecServerQ";
public final static String JMS_USERNAME="jmsuser";       //  The role for this user is "guest" in ApplicationRealm
public final static String JMS_PASSWORD="jms2017Pwd!";
public final static String WILDFLY_REMOTING_URL="http-remoting://secserver.mydomain.com:28080";

此后，客户端可以无任何异常地连接，并且JMS消息开始流动。

暂无
暂无

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

相关问题 如何在Wildfly 10上查找远程JMS队列 JMS + WildFly 8.2.0-从远程jms队列读取 来自远程 ActiveMQ Artemis 的 Wildfly JMS Consumer 如何在Wildfly 10服务器中以编程方式创建JMS队列/主题。 在独立应用程序中为JMS队列创建远程使用者 websphere jms队列从远程客户端访问 如何使用消费者从wildfly jms队列接收消息 wildfly匿名远程jms访问 远程JMS队列的客户端 如何在JBoss的远程JMS队列中编写
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM