Hi all,
 We too have the same problem. Using the stable AMQ 4.1 & stomp, I can
duplicate this problem.

1. Create a durable subscriber, via stomp protocol
2. Publish messages to the topic
3. stop the subscrber
4. stop the producer
5. start the subscriber, using the same client id and "subcription" name.

you will see the "Durable consumer is in use for client" exception.

A workaround, is after setp #4, start producer before step #5.

It would help if others confirm this and as well as the developers take a
note of this. Thanks.

- Sandeep


James.Strachan wrote:
> 
> Could you try using the current 4.1 SNAPSHOT to see if your issue
> still exists as we applied some patches in this area
> 
> 
> On 6/1/06, lathan <[EMAIL PROTECTED]> wrote:
>>
>>
>> In testing a network of brokers (description below) I'm having problems
>> getting a durable consumer to reconnect to a topic if that consumer
>> process
>> is killed (kill -9) and not given a chance to clean up. In looking at the
>> code in TopicRegion.addConsumer it appears to be checking to make sure an
>> active subscription does not already exist for the given clientID. While
>> this does enforce the rule that you can only have one durable
>> subscription
>> for a given client, it seems to preclude the ability to recover when a
>> durable consumer crashes. Am I missing something config-wise or is this a
>> bug?
>>
>> Exception:
>> 2006-05-31 16:41:53,689  [INFO,DemandForwardingBridge] --> Network
>> connection between vm://lab00260102#6 and
>> tcp://localhost/127.0.0.1:60101(lab00260101) has been established.
>> 2006-05-31 16:41:54,450  [INFO,Service] --> Async error occurred:
>> javax.jms.JMSException: Durable consumer is in use for client:
>> NC_lab00260101_inboundlab00260102 and subscriptionName: lab00260102_prov
>> javax.jms.JMSException: Durable consumer is in use for client:
>> NC_lab00260101_inboundlab00260102 and subscriptionName: lab00260102_prov
>>         at
>> org.apache.activemq.broker.region.TopicRegion.addConsumer(TopicRegion.java:80)
>>         at
>>
> 

-- 
View this message in context: 
http://www.nabble.com/Durable-consumer-reconnect-problem-tf1716817s2354.html#a8891464
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to