Is there a way to disconnect an active durable topic subscriber

s where we don't have any control on the client process (say the process is sending large messages which is filling up kahadb partition). Thanks! Abhi -- View this message in context: http://activemq.2283324.n4.nabble.com/Is-there-a-way-to-disconnect-an-active-durable-topic-subscriber-tp4713970

Re: Sometimes any active durable topic subscriber has pending queue message

If you can reproduce it, please open a jira and attach your test case. On Thu, Aug 22, 2013 at 9:39 PM, rafael wrote: > I'm using mqtt with activemq 5.8.0 version. > Sometimes any active durable topic subscriber has pending queue message > like > attached image shown. > I

Sometimes any active durable topic subscriber has pending queue message

I'm using mqtt with activemq 5.8.0 version. Sometimes any active durable topic subscriber has pending queue message like attached image shown. I think that there is no pending queue message if subscriber is online(=active).. Q: Can i check something to research this issue ? Thanks in advanc

Re: ActiveMQ + Stomp durable topic subscriber - website inaccurate

Oct 17, 2012 at 5:40 AM, Peter Hicks wrote: > >> Hello >> >> According to http://activemq.apache.org/stomp.html, one sets >> "activemq.subscriptionName" in a Stomp SUBSCRIBE frame when I want to be a >> durable topic subscriber. However, >> http:/

Re: ActiveMQ + Stomp durable topic subscriber - website inaccurate

org/stomp.html, one sets > "activemq.subscriptionName" in a Stomp SUBSCRIBE frame when I want to be a > durable topic subscriber. However, > http://activemq.apache.org/stomp/stomp10/additional.html says I need to > set > the "durable-subscriber-name" header. > > T

ActiveMQ + Stomp durable topic subscriber - website inaccurate

Hello According to http://activemq.apache.org/stomp.html, one sets "activemq.subscriptionName" in a Stomp SUBSCRIBE frame when I want to be a durable topic subscriber. However, http://activemq.apache.org/stomp/stomp10/additional.html says I need to set the "durable-subscriber-nam

Re: durable topic subscriber using spring and atomikos

more detail in an answer from a while back: http://osdir.com/ml/java.activemq.user/2005-05/msg00141.html On 11 January 2011 22:53, softweave wrote: > > I wrote a topic listener that works fine as a non-durable topic subscriber. I > want to convert it to a durable topic subscriber,

durable topic subscriber using spring and atomikos

I wrote a topic listener that works fine as a non-durable topic subscriber. I want to convert it to a durable topic subscriber, but am running into problems. This portion of the spring configuration sets up the topic listener

Re: Create durable topic subscriber ?

Thanks ! I had called Connection.setClientID(String) before I called Connection.CreateDurableConnectionConsumer(). Something's ok ! -- View this message in context: http://activemq.2283324.n4.nabble.com/Create-durable-topic-subscriber-tp2999808p3001334.html Sent from the ActiveMQ -

Re: Create durable topic subscriber ?

10/18/2010 12:58 AM, quoc_thai wrote: Hi all, From the http://activemq.apache.org/how-do-durable-queues-and-topics-work.html http://activemq.apache.org/how-do-durable-queues-and-topics-work.html I want create a durable topic subscriber but at the consumer, I receive some error "You cann

Create durable topic subscriber ?

Hi all, From the http://activemq.apache.org/how-do-durable-queues-and-topics-work.html http://activemq.apache.org/how-do-durable-queues-and-topics-work.html I want create a durable topic subscriber but at the consumer, I receive some error "You cannot create a durable subscriber wi

Re: How to configure a durable topic subscriber that fails over in a master/slave config?

I've been able to achieve my goal by setting up a durable topic subscriber as a JmsBridgeConnector. lsclark wrote: > > From a Master/Slave broker configuration, I'd like to have the active > master at any given point in time also act as a durable topic subscriber > to

How to configure a durable topic subscriber that fails over in a master/slave config?

>From a Master/Slave broker configuration, I'd like to have the active master at any given point in time also act as a durable topic subscriber to a topic on an external message broker. If a slave takes over as master, I'd like the master to remove its durable topic subscriber, and

Re: [Spam: 5.0] Durable Topic subscriber

>> follows >> >> >> >> >> A Topic publisher is attached to BrokerA (PubA) is publishing 1000 >> messages >> to 'MyTopic'. And the Durable topic subscriber (SubB) attached to BrokerB >> reads the messages from BrokerB. Now to

Re: [Spam: 5.0] Durable Topic subscriber

gle brokers each (BrokerA, BrokerB). The dispatch policy is setup on both brokers as follows A Topic publisher is attached to BrokerA (PubA) is publishing 1000 messages to 'MyTopic'. And the Durable topic subscriber (SubB) attached to BrokerB reads the messages from BrokerB. Now

Re: [Spam: 5.0] Durable Topic subscriber

>> >> >> >> >> >> Also the publisher does Message grouping as well. But when the durable >> >> subscriber goes offline and comes back the messages which are >> published >> >> when >> >> the subscrib

Re: [Spam: 5.0] Durable Topic subscriber

gt; Hi All, >> >> I am trying to get the ordered message delivery for durable Topic >> subscriber. I have setup despatch policy as below >> >> >> >> >> >> Also the publisher does Message grouping

Re: [Spam: 5.0] Durable Topic subscriber

I tried in both 4.1 & 4.2-Snapshot James.Strachan wrote: > > Which version were you using? > > On 3/2/07, Mathulan <[EMAIL PROTECTED]> wrote: >> >> Hi All, >> >> I am trying to get the ordered message delivery for durable Topic >&g

Re: Durable Topic subscriber

Which version were you using? On 3/2/07, Mathulan <[EMAIL PROTECTED]> wrote: Hi All, I am trying to get the ordered message delivery for durable Topic subscriber. I have setup despatch policy as below Also the publisher does Message gr

Durable Topic subscriber

Hi All, I am trying to get the ordered message delivery for durable Topic subscriber. I have setup despatch policy as below Also the publisher does Message grouping as well. But when the durable subscriber goes offline and comes back the