The uri that I am using is this:
failover://(tcp://127.0.0.1:61616
)?startupMaxReconnectAttempts=2&initialReconnectDelay=1
While I'm receiving messages, if I close the broker, I dont receive the
callback onTransportInterrupted, after that, if I startup the broker again,
the client cant reconnect
I want if there is no space to persistence messages that activemq remove all
messages. How can I do that?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Delete-all-messages-tp3300144p3300144.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On Thu, 2011-02-10 at 19:41 +0100, Oscar Pernas wrote:
> Activemq-cpp 3.2.4
> Debian (and tested in windows xp too)
> gcc version 4.4.4 (Debian 4.4.4-1)
>
> This problem only happens if while the consumer is consuming messages, if
> consumer is waiting for new messages, transportInterrupt is recei
Activemq-cpp 3.2.4
Debian (and tested in windows xp too)
gcc version 4.4.4 (Debian 4.4.4-1)
This problem only happens if while the consumer is consuming messages, if
consumer is waiting for new messages, transportInterrupt is received ok...
If I have two consumer of one topic, sometimes one consum
On Thu, 2011-02-10 at 17:29 +0100, Oscar Pernas wrote:
> Hi all,
>
>
> I am testing the transport interrupt and restore of Activemq-CPP over
> topics.
>
> I have a producer sending messages to the broker and a consumer consuming
> them.
>
> If while we are receiving messages, I close the broker
Hi all,
I am testing the transport interrupt and restore of Activemq-CPP over
topics.
I have a producer sending messages to the broker and a consumer consuming
them.
If while we are receiving messages, I close the broker, I can see that Im
not always receiving the transport interrupt message, w
On Thu, 2011-02-10 at 14:14 +, Suneel Papineni wrote:
> Hi,
>
>
>
> I am using ActiveMQ 5.4.2 and NMS 1.5.0. As a producer I want to know
> what are all consumers connected to Message bus and what messages they
> are sending when they got connected or disconnected.
>
> I believe this can b
Hi all,
Since 5.4.2 all messages handle by the consumer remain on the queue forever,
even though they are already processed.
I'm clashing with a problem since the upgrade to 5.4.2. The previous
versions aren't affected by this problem.
The application consists of a spring based consumer which is
Hi,
I am using ActiveMQ 5.4.2 and NMS 1.5.0. As a producer I want to know
what are all consumers connected to Message bus and what messages they
are sending when they got connected or disconnected.
I believe this can be achieved by using Advisory Messages. Using the
link http://activemq.apache
