activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ramit Arora <ramit.ar...@gmail.com>
Subject Re: Consumers not always being released
Date Thu, 27 Mar 2008 18:27:24 GMT

Yeah, I guess doing it the way the website recommends is the correct method
to configure Master/Slave.

Thanks,
Ramit

Mike Miljour wrote:
> 
> I just checked our logs, and I am seeing the same message about the Master
> not being able to connect to the slave.  I will be removing the Network of
> Brokers setting form our config.  We are using queues, not topics.
> Thanks for pointing out the Network of Brokers issue!  I forgot to check
> the logs after we got things working again.
> Mike M
> 
> Ramit Arora wrote:
>> 
>> Hi Mike,
>> Thanks for the reply. I think I understand the way you have set it up
>> now, but doesn't the slave just sit waiting for the lock to be released?
>> As its connectors are not yet started, the store & forward network can't
>> be established. My master keeps complaining that it can't connect to the
>> slave. Can someone from the development team please confirm how shared
>> file system needs to be set up?
>> Anyways, can you please check whether the following test case works on
>> your snapshot (the one you are using is no longer in the repo):
>> 1. Create a producer sending persistent messages to a topic.
>> 2. Create a non-durable topic subscriber.
>> 3. Kill the master when the publisher has sent 100 messages & the
>> subscriber has received 50 messages.
>> 4. Try to receive the remaining 50 messages from the slave.
>> 
>> In my case, step 4 doesn't work. But according to the JMS spec, it
>> should.
>> 
>> Many thanks,
>> Ramit 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Consumers-not-always-being-released-tp15818936s2354p16330165.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message