uhhh... ok. So how do I set that up?
semog wrote:
>
> Hi Eugene,
> The feature you want to use in your situation is called Durable Consumer.
> The Persistence feature is used to ensure that the message will be
> delivered if the broker crashes or is rebooted. The Durable Consumer
> feature is used when the consumer crashes, reboots, or otherwise goes
> offline.
>
> Best,
> Jim
>
> On Tue, Sep 2, 2008 at 7:02 PM, Eugene79 <[EMAIL PROTECTED]> wrote:
>
>>
>> Hi,
>>
>> I am investigating ActiveMQ as a message broker solution for our
>> application. I set it up on my machine and tried sample ruby programs. So
>> far it works fine when there is both a publisher and subscriber running.
>> However, what I want to do is make sure that messages can be delivered
>> even
>> if the subscriber is temporarily unavailable. So, I set up persistence
>> in
>> activemq.xml:
>>
>> <persistenceAdapter>
>> <journaledJDBC journalLogFiles="5" dataDirectory="../data"/>
>> </persistenceAdapter>
>>
>> And changed line 44 in publisher.rb to
>>
>> @conn.send '/topic/event', @body, {'persistent'=>'true'}
>>
>> However, the messages get delivered only if listener.rb is also running.
>> I
>> want to be able to run publisher.rb, have the messages stored by
>> activemq,
>> then run listener.rb and retrieve all the messages that were sent. This
>> doesn't work. How can I set this up?
>>
>> thanks,
>>
>> Eugene
>> --
>> View this message in context:
>> http://www.nabble.com/persistence-not-working-tp19281689p19281689.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/persistence-not-working-tp19281689p19296388.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
