(James, i'm replying to the list - your reply came directly to me) The behavior i've noticed is that if the end consumer is outside of ActiveMQ (e.g., an MDB on a Java EE server, rather than a Camel route configured in activemq.xml), AND the consumer is not running when ActiveMQ starts up, the durable subscriptions don't show up in the console.
Joe Niski IS Development | NWEA PHONE 503.212.3382 | FAX 503.639.7873 NWEA.ORG<3D%22http://www.nwea.org/%22> | Partnering to Help All Kids Learn On 10/22/2010 12:51 AM, James Green wrote: We are reliant on persistent messages lasting up to 3 days. Interestingly I decided to restart AMQ on the test machine which had > 1,000 subscribers and when it came back up the web interface showed they had all disappeared. Does this mean AMQ will not persist a durable subscriber across a restart? James On 21 October 2010 18:19, Joe Niski <joe.ni...@nwea.org><mailto:joe.ni...@nwea.org> wrote: > The only way i've discovered to remove "zombie" durable subscribers (they > were once subscribed, but will never reconnect again) is to delete the > data-store directory. Harsh, and probably not a good idea in a production > environment unless you can guarantee there are no in-flight persistent > messages when you take ActiveMQ down. > > Joe Niski > IS Development | NWEA > > PHONE 503.212.3382 | FAX 503.639.7873 > > NWEA.ORG | Partnering to Help All Kids Learn > > On 10/21/2010 08:55 AM, James Green wrote: > > Hi, > > Due to a bug my side I've managed to create over 1,000 durable topic > subscribers each with differing client-ids. Yep, that equals quite a > mess. > > Somehow I need to unsubscribe these guys. Each was created by the same > PHP script being invoked repeatedly overnight. > > I have created a script that identifies itself as a subscribed > client-id, subscribes to the topic and immediately unsubscribes from > it, however the web interface still shows a subscription for it. The > "Delete" button also merely reloads the page which seems like quite a > bug too... > > I have stomp-level logging switched on and clearly see the client > connecting with the correct ID, and the unsubscribe command for the > right topic coming in. There's no response to this however, should > there be? > > Can anyone advise on what I need to do? AMQ 5.4.0 in use on this > particular instance... > > Thanks, > > James > >
