Re: Mutlicast discovery with persistent topics leads to errors

2008-01-21 Thread tpamsler
I am getting the same error using ActiveMQ 5.0.0: ERROR: Async error occurred: javax.jms.JMSException: Durable consumer is in use for client: NC_spring_inboundsummer and subscriptionName: summer_CLUSTER_SERVICE_TOPIC (2008-01-21 15:25:55,734 VMTransport_org.apache.activemq.broker.TransportConnect

Re: Mutlicast discovery with persistent topics leads to errors

2008-01-14 Thread Jeff Ward
The broker names are always the same. They're set to the name of the host machine (in this case activemq1 or activemq2, depending on which machine). rajdavies wrote: > > Are you consistently setting the broker names - so they are the same > when you bring them up and down ? > On Jan 10, 2008

Re: Mutlicast discovery with persistent topics leads to errors

2008-01-14 Thread Rob Davies
Are you consistently setting the broker names - so they are the same when you bring them up and down ? On Jan 10, 2008, at 9:55 PM, Jeff Ward wrote: I'm using the latest version of ActiveMQ 5.0.0 and I'm having a bit of trouble creating a network of brokers with topics predefined. After brin