[yairogen]

No errors on server.

[yairogen]

Sorry, I missed an error in the log:

04:00:59,287 ERROR [org.hornetq.core.server] HQ224051: Failed to call notification listener: java.lang.IllegalStateException: No queue 894f2ce7-46e5-11e4-84c2-a5dfc9b1d860

        at org.hornetq.core.postoffice.impl.PostOfficeImpl.onNotification(PostOfficeImpl.java:417) [hornetq-server.jar:]

        at org.hornetq.core.server.management.impl.ManagementServiceImpl.sendNotification(ManagementServiceImpl.java:684) [hornetq-server.jar:]

        at org.hornetq.core.server.impl.ServerConsumerImpl.close(ServerConsumerImpl.java:480) [hornetq-server.jar:]

        at org.hornetq.core.server.impl.ServerSessionImpl.doClose(ServerSessionImpl.java:322) [hornetq-server.jar:]

        at org.hornetq.core.server.impl.ServerSessionImpl.access$000(ServerSessionImpl.java:89) [hornetq-server.jar:]

        at org.hornetq.core.server.impl.ServerSessionImpl$1.done(ServerSessionImpl.java:1250) [hornetq-server.jar:]

        at org.hornetq.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:183) [hornetq-server.jar:]

        at org.hornetq.core.server.impl.ServerSessionImpl.close(ServerSessionImpl.java:1241) [hornetq-server.jar:]

        at org.hornetq.core.protocol.stomp.StompProtocolManager$1.run(StompProtocolManager.java:287) [hornetq-stomp-protocol.jar:]

        at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) [hornetq-core-client-2.4.1.Final.jar:]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]

        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]

[gaohoward]

seems that the client send a destination name that doesn't match hornetq's convention. For example it prefixes a '/topic/' to each of its topic destinations, where hornetq's jms topic is always prefixed with 'jms.topic.'.

[yairogen]

ideas how to overcome?

[gaohoward]

Here is a relevant thread Stomp Client 1.5.4 error creating subscription to topic on JBoss HornetQ (Jboss 6.4.2 GA).

It seems there is a way to change the client's destination naming convention (via wireFormat). I think you need to ask the apache.nms team for a solution.