在Jboss EAP 6.3中编写Java程序连接到HornetQ消息服务？

Question

我使用的是Jboss EAP 6.3，需要使用消息传递工具。我在Jboss 4x中工作过，我们可以使用以下代码轻松连接：

public static final String PROVIDER_URL = "jnp://localhost:5445";
   public static final String JNP_INTERFACES = "org.jboss.naming:org.jnp.interfaces";
   public static final String INITIAL_CONTEXT_FACTORY = "org.jnp.interfaces.NamingContextFactory";

   private static Context initialContext;

   public static Context getInitialContextForClient() throws NamingException{
          if(initialContext == null){
                 Properties prop = new Properties();
                 prop.put(Context.INITIAL_CONTEXT_FACTORY, INITIAL_CONTEXT_FACTORY);
                 prop.put(Context.URL_PKG_PREFIXES,JNP_INTERFACES);
                 prop.put(Context.PROVIDER_URL, PROVIDER_URL);
                 initialContext = new InitialContext(prop);
          }
          return initialContext;
   }

上述方法在EAP 6.3中可以连接到HornetQ吗？如果是，还需要哪些配置？另外，我发现在standalone.xml中默认情况下也没有配置1099。

以下是HornetQ在Standalone full中的默认设置。xml文件：

<subsystem xmlns="urn:jboss:domain:messaging:1.4">
        <hornetq-server>
            <persistence-enabled>true</persistence-enabled>
            <journal-type>NIO</journal-type>
            <journal-min-files>2</journal-min-files>

            <connectors>
                <netty-connector name="netty" socket-binding="messaging"/>
                <netty-connector name="netty-throughput" socket-binding="messaging-throughput">
                    <param key="batch-delay" value="50"/>
                </netty-connector>
                <in-vm-connector name="in-vm" server-id="0"/>
            </connectors>

            <acceptors>
                <netty-acceptor name="netty" socket-binding="messaging"/>
                <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">
                    <param key="batch-delay" value="50"/>
                    <param key="direct-deliver" value="false"/>
                </netty-acceptor>
                <in-vm-acceptor name="in-vm" server-id="0"/>
            </acceptors>

            <security-settings>
                <security-setting match="#">
                    <permission type="send" roles="guest"/>
                    <permission type="consume" roles="guest"/>
                    <permission type="createNonDurableQueue" roles="guest"/>
                    <permission type="deleteNonDurableQueue" roles="guest"/>
                </security-setting>
            </security-settings>

            <address-settings>
                <address-setting match="#">
                    <dead-letter-address>jms.queue.DLQ</dead-letter-address>
                    <expiry-address>jms.queue.ExpiryQueue</expiry-address>
                    <redelivery-delay>0</redelivery-delay>
                    <max-size-bytes>10485760</max-size-bytes>
                    <page-size-bytes>2097152</page-size-bytes>
                    <address-full-policy>PAGE</address-full-policy>
                    <message-counter-history-day-limit>10</message-counter-history-day-limit>
                </address-setting>
            </address-settings>

            <jms-connection-factories>
                <connection-factory name="InVmConnectionFactory">
                    <connectors>
                        <connector-ref connector-name="in-vm"/>
                    </connectors>
                    <entries>
                        <entry name="java:/ConnectionFactory"/>
                    </entries>
                </connection-factory>
                <connection-factory name="RemoteConnectionFactory">
                    <connectors>
                        <connector-ref connector-name="netty"/>
                    </connectors>
                    <entries>
                        <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
                    </entries>
                </connection-factory>
                <pooled-connection-factory name="hornetq-ra">
                    <transaction mode="xa"/>
                    <connectors>
                        <connector-ref connector-name="in-vm"/>
                    </connectors>
                    <entries>
                        <entry name="java:/JmsXA"/>
                    </entries>
                </pooled-connection-factory>
            </jms-connection-factories>

            <jms-destinations>
                <jms-queue name="ExpiryQueue">
                    <entry name="java:/jms/queue/ExpiryQueue"/>
                </jms-queue>
                <jms-queue name="DLQ">
                    <entry name="java:/jms/queue/DLQ"/>
                </jms-queue>
            </jms-destinations>
        </hornetq-server>
    </subsystem>

以下是同一文件中的套接字绑定：

<socket-binding name="messaging" port="5445"/>
    <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
    <socket-binding name="messaging-throughput" port="5455"/>

因为在Jboss EAP 6.3中无法看到org . jnp . interfaces . namingcontextfactory类，所以我尝试如下:

prop.put(Context.PROVIDER_URL,"localhost:5445"); 
prop.put(Context.INITIAL_CONTEXT_FACTORY,"org.hornetq.core.remoting.impl.netty.NettyConnectorFactory");
prop.put(Context.URL_PKG_PREFIXES,"org.jboss.naming:org.jnp.interfaces");

目前，它正在引发连接异常。

谁能建议或提交一个java程序，说明如何在Jboss EAP 6.3中实现与Hornetq的连接？

更新：我仍然不知道我是否遵循了正确的程序。

以下是我得到的例外情况：

javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.jnp.interfaces.NamingContextFactory from classloader ModuleClassLoader for Module 

我检查了它在bin/client中的jboss-client.jar，发现上面的界面不存在，但存在于包含jbiss-allclient.jar.的以前的版本中，我不认为把它放在这个jboss版本中是正确的。

Answer 1

单击此jboss链接；其中包含解决上述问题的快速入门程序。

1）下载代码；在netbean中导入运行jboss-helloworld-jms的pom.xml。运行干净的构建。

2）使用此链接解决maven构建问题：找不到Pom

3)下面是用于连接服务器的代码片段

private static final String DEFAULT_MESSAGE = "Hello, World!";
private static final String DEFAULT_CONNECTION_FACTORY = "jms/RemoteConnectionFactory";
private static final String DEFAULT_DESTINATION = "jms/queue/test";
private static final String DEFAULT_MESSAGE_COUNT = "1";
private static final String DEFAULT_USERNAME = "quickstartUser";
private static final String DEFAULT_PASSWORD = "quickstartPwd1!";
private static final String INITIAL_CONTEXT_FACTORY = "org.jboss.naming.remote.client.InitialContextFactory";
private static final String PROVIDER_URL = "remote://localhost:4447";

String connectionFactoryString = System.getProperty("connection.factory", DEFAULT_CONNECTION_FACTORY);
log.info("Attempting to acquire connection factory \"" + connectionFactoryString + "\"");
connectionFactory = (ConnectionFactory) context.lookup(connectionFactoryString);
log.info("Found connection factory \"" + connectionFactoryString + "\" in JNDI"); 

4)创建用户“quick start User”/“quick start pwd 1！”，在Jboss EAP 6.3中；在应用领域中使用adduser.bat

5）检查这些jms/队列/测试和jms/远程连接工厂是否存在于独立.xml。

6)将代码作为简单的Java应用程序运行，魔法就在那里。

Answer 2

根据您的堆栈跟踪，我认为您没有熟练使用JBoss EAP 6.3的旧JNDI设置

发件人：http://blog.akquinet.de/2014/09/26/jboss-eap-wildfly-three-ways-to-invoke-remote-ejbs/

Properties prop = new Properties();

prop.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");

prop.put(Context.PROVIDER_URL, "http-remoting://127.0.0.1:8080");
prop.put(Context.SECURITY_PRINCIPAL, "username");
prop.put(Context.SECURITY_CREDENTIALS, "password");

prop.put("jboss.naming.client.ejb.context", false);
prop.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");

Context context = new InitialContext(prop); 

应用程序无法实例化initialContext，这是一个您应该关注的问题。

另外，对我来说，消息队列和您的jndi都试图连接localhost：5445，这对我来说有点奇怪。