activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Buchi Reddy B (JIRA)" <>
Subject [jira] [Commented] (AMQ-3874) Unable to destroy a durable subscription
Date Wed, 13 Jun 2012 14:55:43 GMT


Buchi Reddy B commented on AMQ-3874:

No. We have not tested it with 5.6.0. But, have you fixed this in 5.6.0? Can you point to
the JIRA ticket if so?
> Unable to destroy a durable subscription
> ----------------------------------------
>                 Key: AMQ-3874
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: solaris, linux
>            Reporter: Bhanu
> I think theres an issue that occurs sometimes while removing durable subscriptions from
the broker. This has hit us second time in a week that when a perl durable subscriber using
stomp goes down, it is not shown as inactive in broker. Even though there were no active connections(did
a thorough lsof check) somehow broker thought that the subscriber was active. Whats more worse
is trying to destroy that subscription via jconsole gives an error :
> "Problem invoking destroy: java.rmi.UnmarshallException: Error unmarshalling return;
nested exception is java.lang.ClassNotFoundException: javax.jms.InvalidDestinationException
(no security manager: RMI class loader disabled)"
> Since we cannot destroy this subscription, the client cannot come up with the same client
Id and subscription name. This is not reproducible easily
> but is some weird corner case. Can somebody please check. Let me know if you have more
> Thanks & Regards
> Bhanu

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message