1 Reply Latest reply on Jun 9, 2016 7:14 AM by Miroslav Novak

    JBOSS 6.4 javax.jms.JMSSecurityException: HQ119031: Unable to validate user: null question

    Prem Mishra Newbie

      Hi All,

                 We have a scenario where  on JBOSS 6.4 ,we have 2 nodes which need to talk with each other using JMS. Lets assume the following:


      Node1:JMS provider

      Node2:JMS Client


      I have configured Node2 to use local connectionfactory and use an outbound socket binding to point to Node1 on port 5545 (added offset of 100 to  5445) . When I make a test call on Node2 ,I get the below exception:


      HQ119031: Unable to validate user: null

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:399)

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:880)

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:789)

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:324)

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:654)

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:676)

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:107)

      13:56:29,063 INFO  [stdout] (Dispatcher-Thread-100) at org.hornetq.jms.client.HornetQConnectionFactory.createConnection


      I have tried setting <security-enabled>false</security-enabled> on both node1 and node2 ,but it does not help.The JMS client in node2 is part of a product installation which uses JMS internally ,so I cannot force it to use a credential for connectionfactory.

      When both  JMS client and JMS server are on same node say for example Node2 and I use in-vm connector,all works well.


      Please suggest some alternatives which I can try  overcome the issue.



      Thank You,