I try since couple of hours and i didn't find out the solution.
I would like 2 brokers replicated with context
so if one broker dies, i'll not lose data.
when i tried network-broker, my broker 1 et broker 2 don't have the same
messages... so if i kill broker 1, i lose his data
any idea?
--
V
I am using active MQ with spring.
I am using JMS Template to send the messages.
My application logic is the following activies in sequence
1> Do some set of online activities
2> Submit some things for offline activity using JMS template and active MQ
3> Sent response for online activities
My u
Hi,
I'm not sure I understand your requirement. One broker (with multiple
slaves) can use single instance of KahaDB. You cannot use same KahaDB
for different brokers and also KahaDB can't be replicated. Maybe you
want to explore network of brokers
http://activemq.apache.org/networks-of-brokers.htm
Thanks. That will be my first plugin, so let's try it :-)
Original-Nachricht
> Datum: Mon, 3 Dec 2012 13:24:02 +
> Von: Gary Tully
> An: "users@activemq.apache.org"
> Betreff: Re: MQTT and JMS/NMS: ActiveMQ vs. Apollo
> That would be a good use of a broker plug in. overrid
That would be a good use of a broker plug in. override addConnection and
removeConnection and if there is a duplicate clientId, remove the old
connection before progressing.
It may be possible to grok the protocol also and make it conditional.
Essentially, this would workaround the jms specific be
Hi,
I can reproduce this behaviour by simply turning the mobile data (3G) off and
on again. Then, my Android service starts reconnecting to the ActiveMQ server
and fails.
The problem is, that after reconnecting to my mobile network provider it might
happen that I get a new IP adress which requ
On the Apollo side, the "rich protocol" conversions aren't there yet:
https://issues.apache.org/jira/browse/APLO-267
For ActiveMQ 5.7 seems like the dead connection isn't being cleaned up
properly when it goes away. Is this something you can reproduce?
On Mon, Dec 3, 2012 at 4:56 AM, Christian W
Hi,
I'm currently trying to add mobile clients (Android, eclipse paho client API)
via the MQTT protocol to our ActiveMQ and Apollo server. The other clients use
JMS/NMS. Transport connectors are correctly defined.
I have experienced following problems:
Using ActiveMQ 5.7:
Everthing seems to
two things would help understand:
1) a thread dump of the broker... to see where the send it waiting
2) some snippets from the broker log ... to see relevant usage limits that
are hit
On 3 December 2012 10:42, Geurt Schimmel wrote:
> Hi,
>
> Using a destinationPolicy for dealing with large mess
Hi,
Using a destinationPolicy for dealing with large messages (23Mb):
My broker hangs on flowcontrol as the topic has reached the 30Mb boundary - why
? Sending just 1 message of 23Mb by splitting it into chunks of 1
10 matches
Mail list logo
