验证问题,然后使用来自远程主机的Wildfly ActiveMQ

时间:2016-06-14 14:11:07

标签: jms wildfly

我很抱歉可能是一个简单的问题。 我在Wildfly上使用ActiveMQ。在本地机器上工作时没有出现任何问题。但随后我的客户端应用程序移动到远程主机我开始收到以下错误:

javax.naming.AuthenticationException: Failed to connect to any server. Servers tried: [http-remoting://10.76.46.211:8080 (Authentication failed: all available authentication mechanisms failed:
   JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Failed to read server challenge [Caused by java.io.FileNotFoundException: C:\work\wildfly-10.0.0.Final\standalone\tmp\auth\local7244391904621911627.challenge (No such file or directory)]
   DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Cannot perform callback to acquire realm, authentication ID or password [Caused by javax.security.auth.callback.UnsupportedCallbackException])] [Root exception is javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
   JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Failed to read server challenge [Caused by java.io.FileNotFoundException: C:\work\wildfly-10.0.0.Final\standalone\tmp\auth\local7244391904621911627.challenge (No such file or directory)]
   DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Cannot perform callback to acquire realm, authentication ID or password [Caused by javax.security.auth.callback.UnsupportedCallbackException]]
        at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:238)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
        at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
        at javax.naming.InitialContext.lookup(InitialContext.java:411)
        at com.emc.PerfRPQA.ATestAgent.taConsumer.run(taConsumer.java:87)
        at com.emc.PerfRPQA.ATestAgent.ATestAgent.main(ATestAgent.java:71)
Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
   JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Failed to read server challenge [Caused by java.io.FileNotFoundException: C:\work\wildfly-10.0.0.Final\standalone\tmp\auth\local7244391904621911627.challenge (No such file or directory)]
   DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Cannot perform callback to acquire realm, authentication ID or password [Caused by javax.security.auth.callback.UnsupportedCallbackException]
        at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:114)
        at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:389)
        at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241)
        at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
        at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199)
        at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113)
        at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
        at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092)
        at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
        at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
        at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)
        at org.xnio.nio.WorkerThread.run(WorkerThread.java:559)
        at ...asynchronous invocation...(Unknown Source)
        at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:294)
        at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:275)
        at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:379)
        at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:363)
        at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:111)
        at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:197)
        ... 9 more
Exception in thread "main" java.net.UnknownHostException: RHEL1: RHEL1: Name or service not known
        at java.net.InetAddress.getLocalHost(InetAddress.java:1438)
        at com.emc.PerfRPQA.ATestAgent.ATestAgent.main(ATestAgent.java:76)
Caused by: java.net.UnknownHostException: RHEL1: Name or service not known
        at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
        at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:866)
        at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1258)
        at java.net.InetAddress.getLocalHost(InetAddress.java:1434)
        ... 1 more

这是JMS的配置

<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
    <server name="default">
        <cluster password="ATest" user="ATestAgent"/>
        <security-setting name="#">
            <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
            <role name="ATestAgent" 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"/>
        <jms-queue name="ATestQ" entries="java:jboss/exported/jms/queue/ATestQ"/>
        <jms-topic name="ATestT" entries="java:jboss/exported/jms/topic/ATestT"/>
        <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
        <connection-factory name="RemoteConnectionFactory" thread-pool-max-size="1024" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/>
        <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
    </server>
</subsystem>

我使用ATestQ和ATestT。

我已经双重验证确实使用了用户正确创建并在I-net中找到的其他东西作为潜在问题。但没有解决问题。

有任何建议吗?

提前致谢

0 个答案:

没有答案
相关问题