Yah so virtual topics can behave like queues under the covers.
But not sure I follow you here:
Failover is good for external
> clients, which will connect to the surviving broker.
>
> Maybe because I'm not getting exactly what these "messages from inside the
server" are.
Sounds like you want a fa
A durable consumer won't receive messagew sent before it was started if
it has never subscribed to the broker before. The purpose of a durable
consumer is to allow a consumer to disconnect and then reconnect and
receive any messages sent since the last time it was connected. So if
you are startin
Are you using a fixed clientID and subscriberName?
2009/1/26 zunrise :
>
> First thx for quick reply. I'm already using durableconsumers. My
> subscribition Client is written in .net and I'm using NMS. Can anyone send
> me a sample code how to let it work. The problem is that the message isn't
> s
First thx for quick reply. I'm already using durableconsumers. My
subscribition Client is written in .net and I'm using NMS. Can anyone send
me a sample code how to let it work. The problem is that the message isn't
send to durable consumer, if the consumer subscribes first time after a
message is
Sending to a topic that has no subscribers won't by default hold the
message until someone subscribes. You could use retroactive consumers,
or durable consumers to solve this, or switch to using a queue if that
would meet your needs.
You may want to read the JMS tutorial to get a feel for when
