[ 
https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary Tully resolved AMQ-6587.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 5.15.0

> Failed to remove inactive destination Topic: Destination still has an active 
> subscription
> -----------------------------------------------------------------------------------------
>
>                 Key: AMQ-6587
>                 URL: https://issues.apache.org/jira/browse/AMQ-6587
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.15.0
>
>
> broker setSchedulePeriodForDestinationPurge, wildcard topic subscriber and 
> anonymous publishers to new destinations. 
> Race between addDestination and markForGc and canGc
> {code}
> ERROR region.RegionBroker: Failed to remove inactive destination Topic: 
> destination=A.4725, subscriptions=1
> javax.jms.JMSException: Destination still has an active subscription: 
> topic://A.4725
>       at 
> org.apache.activemq.broker.region.AbstractRegion.removeDestination(AbstractRegion.java:271)
>       at 
> org.apache.activemq.broker.region.RegionBroker.removeDestination(RegionBroker.java:354)
>       at 
> org.apache.activemq.broker.BrokerFilter.removeDestination(BrokerFilter.java:179)
>       at 
> org.apache.activemq.broker.BrokerFilter.removeDestination(BrokerFilter.java:179)
>       at 
> org.apache.activemq.broker.BrokerFilter.removeDestination(BrokerFilter.java:179)
>       at 
> org.apache.activemq.broker.region.RegionBroker.purgeInactiveDestinations(RegionBroker.java:897)
>       at 
> org.apache.activemq.broker.region.RegionBroker$1.run(RegionBroker.java:118)
>       at 
> org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
>       at java.util.TimerThread.mainLoop(Timer.java:555)
>       at java.util.TimerThread.run(Timer.java:505)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to