Getting alerted that a queue does not exist with stomp send?

[tomjenkinson]

Hi,

I am sending a message to a non-existant queue using Stomp on HornetQ and am expecting to get an error back but am just getting a receipt?

I have installed Stomp and can send messages to existant destinations just fine (this was really easy - congratulations!).

However now I am trying to get the error this is not working?

I have tried this from code but for ease of discussion I am going to paste in a telnet session that replicates the issue:

(Also note that I tried both the destination name of jms.queue.nothetetet and /queue/nottheretest

[tom@localhost ~]$ telnet localhost 61613
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
CONNECT
login:guest
passcode:guest

^@
CONNECTED
session:1776663472

SEND
destination:jms.queue.nothetetet
receipt:send-xyz

hello?
^@
RECEIPT
receipt-id:send-xyz

Hope you can help me!

Tom

[tomjenkinson]

To clarify, I was expecting an ERROR frame, rather than the RECEIPT frame.

Tom

[ataylor]

The Stomp protocol does not specify what should happen in this case, its up to the server implementation as far as i understand it.

[tomjenkinson]

Thanks for the feedback Andy, is there any way a client can determine if a queue exists or not from the stomp protocol?

[ataylor]

not at present, we may be able to add something tho, feel free to raise a jira

[tomjenkinson]

Thanks Andy, will do.

[timfox]

Andy Taylor wrote:

not at present, we may be able to add something tho, feel free to raise a jira

It should be possible already.

You should be able to use the management API over the STOMP connection. After all the management API is accessible to any client by sending messages to the special management address, just the same as in JMS. This is covered in the user manual.

[clebert.suconic]

I believe he's talking about throwing an exception case the destination doesn't exist, not how to do a query through management for an existent destination.

Other providers such as ActiveMQ will auto-create the JMS queue for a stomp queue, and I have seen some users complaining about it. I'm not sure yet if we should add a setting or not.. but I have seen users complaining/requesting this kind of thing.

[tomjenkinson]

Hi,

You are correct, I would prefer an exception in the case that the destination doesn't exist. I could do what Tim suggested but it leaves a window where I can send a message to an "empty sink".

1. User1 checks destinationA exists say by using management API over Stomp

2. User1 receives response that destinationA exists

3. User2 deletes destinationA

4. User1 sends a message to destinationA, without an exception he now believes the message has been queued but actually the queue was delete by User2 in step 3 above so the message has been silently discarded

Hope this clarifies,

Tom

[tomjenkinson]

When I said "exception" I meant ERROR frame from Stomp - sorry