Where can you find the durable subscribers of the virtual topic?Virtual topic is not a real topic and it's transformed into queues by demand in runtime.So you can think it as a combination of queues.You can see the subscribers of the Virtual topic in Queue view page in web console.
At 2013-01-24 00:36:51,"Marcos A. Reynoso" <marc...@epidataconsulting.com> wrote: >Hi everyone, > >I'm having a problem deleting offline durable subscribers (both from >the activeMQ web console or unsubscribing) causing the storage to get >filled. > >Then, in the ActiveMQ web console I press delete on the offline >subscriber and it disappears, but the topic does not reduce the Number >Of Consumers. When restarting the broker, the offline subscriber >appears again. > >I found that this happens when I use virtual topics. > >If someone knows what might be happening I will be very grateful > >Thanks >Marcos > >--------------------- >This is my setup: > >java version "1.6.0_31" >ActiveMQ 5.7(standalone) >OS: Red Hat Enterprise Linux Server release 5.8 (Tikanga) (kernel >2.6.18-308.el5) > >My activemq.xml: > ><beans > xmlns="http://www.springframework.org/schema/beans"; > xmlns:amq="http://activemq.apache.org/schema/core"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://www.springframework.org/schema/beans >http://www.springframework.org/schema/beans/spring-beans.xsd > http://activemq.apache.org/schema/core >http://activemq.apache.org/schema/core/activemq-core.xsd > http://activemq.apache.org/camel/schema/spring >http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";> > > <!-- Allows us to use system properties as variables in this >configuration file --> > <bean > class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> > > <broker xmlns="http://activemq.apache.org/schema/core"; >brokerName="static-broker1" dataDirectory="${activemq.data}"> > ><!-- Destination specific policies using destination names or wildcards --> > <destinationPolicy> > <policyMap> > <policyEntries> > <policyEntry queue=">" producerFlowControl="true" >memoryLimit="20mb"> > <deadLetterStrategy> > <individualDeadLetterStrategy >queuePrefix="DLQ." useQueueForQueueMessages="true" /> > </deadLetterStrategy> > </policyEntry> > <policyEntry topic=">" producerFlowControl="true" >memoryLimit="20mb"> > </policyEntry> > </policyEntries> > </policyMap> > </destinationPolicy> > > <!-- Use the following to configure how ActiveMQ is exposed in JMX --> > <managementContext> > <managementContext createConnector="true"/> > </managementContext> > > <networkConnectors> > </networkConnectors> > > <persistenceAdapter> > <kahaDB directory="${activemq.data}/static-broker1/kahadb" /> > </persistenceAdapter> > > <!-- The maximum amount of space the broker will use before >slowing down producers --> > <systemUsage> > <systemUsage> > <memoryUsage> > <memoryUsage limit="20 mb"/> > </memoryUsage> > <storeUsage> > <storeUsage limit="1 gb" name="foo"/> > </storeUsage> > <tempUsage> > <tempUsage limit="100 mb"/> > </tempUsage> > </systemUsage> > </systemUsage> > > <destinationInterceptors> > <virtualDestinationInterceptor> > <virtualDestinations> > <virtualTopic name=">" >prefix="VirtualTopicConsumers.*." /> > </virtualDestinations> > </virtualDestinationInterceptor> > </destinationInterceptors> > > <transportConnectors> > <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/> > </transportConnectors> > > </broker> ><import resource="jetty.xml"/> > ></beans>
