1 Reply Latest reply on Feb 6, 2014 12:50 PM by mattso

    PasswordCrackingQueue not found

    mattso

      Hi all,

       

        I am using EAP 6.1 final, and we were trying to use the standalone-full profile.  However, JSR77 is not working with the jmx-console port that we have so we decided to remove the JSR77 subsystem from the profile configuration.

        We use remote RMI call extensively via a ported version of twiddle, and we have setup a single management user for the remote RMI authentication purpose.

        We then started adding datasource, modules, logging and finally JMS queue setup to the configuration.  All seems to work well until we start doing some business logic, and we see the following exception:

       

      2014-02-05 17:45:05,903 DEBUG [Thread-330][server] Sending exception to client: HornetQException[errorType=QUEUE_DOES_NOT_EXIST message=HQ119017: Queue jms.queue.passwordCrackingQueue does not exist]

              at org.hornetq.core.server.impl.ServerSessionImpl.createConsumer(ServerSessionImpl.java:348)

              at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:218)

              at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631)

              at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547)

              at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523)

              at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564)

              at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160)

              at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

              at java.lang.Thread.run(Thread.java:744)

       

        We do not define this queue and I think it has something to do with HornetQ setup?  Any idea / advice?  Many thanks in advance!

       

      Regards,

      Matthew