Wxman wrote:
>
> But, looking at my code, it creates durable subscriptions to topics in my
> *consumer* code. There is no reference to durable messages in the
> producer code. So, am I leaving something out? (I must be, because my
> app doesn't seem to behave in the way
bsnyder wrote:
>
> Two points within JMS that are often confused are message durability
> and message persistence. Though they are similar, there are some
> semantic differences but each has its specific purpose. Message
> durability can only be achieved with the pub/sub domain. When clients
> c
bsnyder wrote:
>
> The default configuration in ActiveMQ 5.3 will persist messages using
> KahaDB:
>
> http://activemq.apache.org/kahadb.html
>
> This will persist messages between broker restarts. But this will only
> work if the messages are marked for persistence by the message
> producer:
I'm using AMQ 5.3.0... My programs successfully send and receive messages
through the broker. However, this only happens for messages sent after its
launch. Messages that were submitted *prior* to my app's launch are *not*
received. My understanding of persistence is that this is the point of
will soon bog down my program...
Wxman
--
View this message in context:
http://www.nabble.com/Clearing-the-message-store-tp24634974p24634974.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
