Ooops, my-bad. The delivery mode is set to PERSISTENT. I was not using the
producer's setDeliveryMode method :o)
Joe
James.Strachan wrote:
>
> On 9/5/07, ttmdev <[EMAIL PROTECTED]> wrote:
>>
>> I am doing the following:
>>
>> 1. I start a broker with persitent="false" and no destinations def
On 9/5/07, ttmdev <[EMAIL PROTECTED]> wrote:
>
> I am doing the following:
>
> 1. I start a broker with persitent="false" and no destinations defined in
> it's xml cfg file.
> 2. I then start a producer that looks up a queue, called Q.REQ, via the
> Context.lookup() approach
> 3. The producer sends
I am doing the following:
1. I start a broker with persitent="false" and no destinations defined in
it's xml cfg file.
2. I then start a producer that looks up a queue, called Q.REQ, via the
Context.lookup() approach
3. The producer sends 20 messages to the queue called Q.REQ w/delivery mode
se
On 9/4/07, tmi <[EMAIL PROTECTED]> wrote:
>
> Any JMS destinations that you create in your Java producer/consumer using
> javax.jms.Session.createQueue() or createTopic() will not outlive a restart
> of ActiveMQ.
They will if you use persistent messaging and you don't consume all
the messages on a
On 8/29/07, srasul <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> ActiveMQ makes it very easy to create JMS Destinations, but seems like they
> are not every easy to destroy.
Its pretty easy via JMX...
> does this mean that i will case ActiveMQ to crash if i create too many JMS
> Destinations?
No (provi
Any JMS destinations that you create in your Java producer/consumer using
javax.jms.Session.createQueue() or createTopic() will not outlive a restart
of ActiveMQ.
Queues/topics that you want to outlive a broker restart need to be created
directly in the broker, e.g. using some sort of JMX consol
