Is it really a workaround? I was under the impression that was the
actual expected use case, and its the only example given in the docs.
On Wed, 16 Mar 2022 at 13:39, Justin Bertram wrote:
>
> Is the work-around I outlined viable for you or are you waiting on the fix?
>
>
> Justin
>
> On Wed, Mar
Is the work-around I outlined viable for you or are you waiting on the fix?
Justin
On Wed, Mar 16, 2022 at 6:01 AM Frison, Louisa (EXT) <
louisa.fri...@union-investment.de> wrote:
> Cool, I just opened a ticket for it, thanks for taking the time to answer
> my question !
>
> Louisa
>
>
This is indeed the right list for your question. :)
In short, I think this is a bug. Please open a Jira [1].
That said, I think there's a simple work-around - just treat the
subscription queue like a normal JMS queue. For example:
ActiveMQConnectionFactory cf = new ActiveMQConnectionFacto
Thank you for answering.
This is the scenario:
(embedded) broker A <---> standalone broker B <---> (embedded) broker C
it is a hub-and-spoke network of brokers, so broker B gets and dispatches
all messages.
we start establishing the connection for all the brokers and start sending
messages from
Not sure I did understand your scenario. Can you please describe it again using
broker names A,B and C?
> when we disconnect one of
> the embedded brokers from the network, it does not get the pending messages
A broker that is disconnected from the network won't be able to get any
messages rig
We've been playing a little bit more, and we faced another issue.
Having a network of brokers, two of them embedded on a java application
connect to a central standalone activemq server, when we disconnect one of
the embedded brokers from the network, it does not get the pending messages
from the
Attached to JIRA issue: https://issues.apache.org/jira/browse/AMQ-3353
However, we've found that closing the session and reopening it solves the
problem.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Durable-subscriptions-not-surviving-network-disconnect-tp3586149p364827
Can you raise a Jira and attach this, so it doesn't get lost in emails?
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nightta
This JUnit test reproduces the error: http://pastebin.com/RXCVHzGt
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Durable-subscriptions-not-surviving-network-disconnect-tp3586149p3646615.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I've started a JUnit Test case.
Since it's the first time, it's not clean, may be buggy and the behavior is
not what I really expected, but maybe it's a start.
org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest:
http://pastebin.com/kr9uu0uE
--
View this message in context:
Thanks Gary.
I'm using ConnectionInfo and RemoveInfo to detect (re)connections.
However, I'm trying to tell the client to (re)subscribe againt to the topic,
like if I restarted the whole client, but it's not working.
I've been playing with TransportListener and some advisory message (don't
know w
There is a transport listener interface that can give you indications
of reconnects.
see: org.apache.activemq.ActiveMQConnection#addTransportListener
For a unit test, have a look at:
org.apache.activemq.usecases.BrokerQueueNetworkWithDisconnectTest
this uses a socket proxy to simulate a network f
Sorry for the late response.
There is already a Jira issue
(https://issues.apache.org/jira/browse/AMQ-3353).
While I do know how to reproduce it using multicast brokers and producer and
consumer from the example directory, I do not know how to make a junit case.
If it's not difficult, I could try
can you raise a jira with your description or try and recreate in a
junit test case
On 23 June 2011 11:50, Andreas Calvo wrote:
> We've been stuck with the same problem (in a different scenario).
> We've tried to replicate the same behavior using the examples on activemq
> (ant producer, ant cons
We've been stuck with the same problem (in a different scenario).
We've tried to replicate the same behavior using the examples on activemq
(ant producer, ant consumer, and static-network-broker), and, as Joe said,
the activemq seems to reconnect just fine, but the clients get stuck.
--
View this
But in 4.1, if we have durable subscribers, we need not send persistent
messages for subscriber to get them after it is back. I mean, if durable
subscriber is down for some time, and mean while if publisher send some
messages, and when the the durable subscriber is back, it will receive all
messag
found :)
the problem was that every sent message wasn't persistent, now
it's working. i didn't know i had to enable persistance for every
message to be able to be retrieved by a durable subscription.
I think that i missed the documentation on that!
thanks again,
yari
James Strachan ha scritto:
>
2008/9/29 Yari Marchetti <[EMAIL PROTECTED]>:
> oki, this makes sense indeed, and now i understand why
> i keep on getting always the same message every time.
>
> But now my problem is on durable subscription because
> if i can't get messages that were delivered while i was
> disconnected. For exam
oki, this makes sense indeed, and now i understand why
i keep on getting always the same message every time.
But now my problem is on durable subscription because
if i can't get messages that were delivered while i was
disconnected. For example:
1) 'A' makes a durable subscription to 'test' topic
subscription recovery policy is for non-durable topic subscribers
2008/9/26 Yari Marchetti <[EMAIL PROTECTED]>:
> Hi everyone,
> i was playing with durable subscriptions and observed a
> behavior that seems strange to me. I configured ActiveMQ
> with
>
>
>
> for every topic, and then created a du
Reading the link you provided, i found that:
"So we support a timed or fixed size recovery buffer so that
if you reconnect to another broker within some time period
(...), then *any messages you missed during the downtime*
are redelivered before new messages are delivered to you."
so i tried this
On Fri, Sep 26, 2008 at 7:32 AM, Yari Marchetti
<[EMAIL PROTECTED]> wrote:
> Hi everyone,
> i was playing with durable subscriptions and observed a
> behavior that seems strange to me. I configured ActiveMQ
> with
>
>
>
> for every topic, and then created a durable subscriber for topic
> "test" wi
On 6/4/07, keneida <[EMAIL PROTECTED]> wrote:
To monitor ActiveMQ I use jconsole. In MBeans, there is a tree view with
following branch org.apache.activemq; name og broker; Subscription; Durable;
Subscription name; Topic; client ID
For each client i can browse the messages. What kind of message
nection();
> HerbieConnection.setClientID("CMD");
> HerbieConnection.start();
-Original Message-
From: wallace [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 25, 2007 10:40 AM
To: users@activemq.apache.org
Subject: Re: durable subscriptions
Where can I find the conf/context.xml?
Where can I find the conf/context.xml? I only see activemq.xml in conf.
Thanks,
-Wallace
--
View this message in context:
http://www.nabble.com/Re%3A-durable-subscriptions-tf3162851s2354.html#a10185868
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
James Strachan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 12:50 PM
To: users@activemq.apache.org
Subject: Re: durable subscriptions not working
Do you create the subscriber first before running the publisher?
On 2/9/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
>
I create the publisher first and then the subsciber
-Original Message-
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 12:50 PM
To: users@activemq.apache.org
Subject: Re: durable subscriptions not working
Do you create the subscriber first before
Do you create the subscriber first before running the publisher?
On 2/9/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
Hello active mq users ,
I have Java 1.5.09 , Tomcat 5.5 .
I am using the following active mq jars activemq-core-4.0.1.jar ,
backport-util-concurrent-
On 2/6/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
Thank you so much James.
Which version of active mq support durable subscriptions,
All of them since 1.0
As of now, I am using the following jars , in regard to active mq
activemq-core-4.0.1.jar
backport-util-concurrent-2.1.ja
ers@activemq.apache.org
Subject: Re: durable subscriptions
On 2/6/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
> Thanks for the information. As per the JMS documentation , Sessions
> with durable subscriptions, should specify a Client Identifier I am
> using Java 1.5 and T
On 2/6/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
Thanks for the information. As per the JMS documentation , Sessions with
durable subscriptions, should specify a Client Identifier
I am using Java 1.5 and Tomcat 5.5.20 .
Where should I specify the client identifier ?
The code tha
02, 2007 4:12 AM
To: users@activemq.apache.org
Subject: Re: durable subscriptions
On 2/2/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
> Hello activemq users ,
>In my project we'll be using durable subscriptions. Is
> there any example or code sampl
On 2/2/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
Hello activemq users ,
In my project we'll be using durable subscriptions. Is
there any example or code sample which explains the usage of durable
subscriptions using active mq ?
There's no real difference with dura
33 matches
Mail list logo
