-
1. Re: Core bridge: sending messages to non-existent queue name (HornetQ to Wildfly)
gaohoward Jan 22, 2015 8:58 AM (in response to lostvicking)I think it's developer's responsibility to make sure the queue actually exists. From core bridge point of view, it forwards messages from a source queue to an address, not a queue.
Howard
-
2. Re: Core bridge: sending messages to non-existent queue name (HornetQ to Wildfly)
lostvicking Jan 23, 2015 2:05 AM (in response to gaohoward)I respect that it is up to the developer to ensure the queue exists, however, from a guaranteed delivery point of view I would have expected the message to be returned to the originating queue in this instance. Vic
-
3. Re: Core bridge: sending messages to non-existent queue name (HornetQ to Wildfly)
ataylor Jan 23, 2015 4:04 AM (in response to lostvicking)what guarantee do you mean? maybe you are misunderstanding how the core API works, messages are sent to an address, this address can have 0 or more queue bound to it, the guarantee in this case is that the message successfully arrived at the address, which it did. The fact that there are no queues bound to it makes no difference.
-
4. Re: Core bridge: sending messages to non-existent queue name (HornetQ to Wildfly)
lostvicking Jan 23, 2015 4:45 AM (in response to ataylor)Maybe I'm using the wrong functionality here. What I am looking for is to reliably forward a message between 2 queues across a network connection. It is imperative that if the message does not arrive at the remote queue (for any reason) that it remains in the local queue. Is there a mechanism I could employ to achieve this goal?
-
5. Re: Core bridge: sending messages to non-existent queue name (HornetQ to Wildfly)
ataylor Jan 23, 2015 5:38 AM (in response to lostvicking)if you have your target address configured correctly with your queue then this will happen.