On 2/9/07, Sandeep Chayapathi <[EMAIL PROTECTED]> wrote:
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.
AFAIK this should work fine against 4.2-SNAPSHOT as we recently fixed a bug that was causing the stomp connection to stick around on the broker after the stomp client had been stopped. -- James ------- http://radio.weblogs.com/0112098/
