I just tried with the latest (today's code) and 5.5.1 and 5.6.0. They seem
to make the duplex connection just fine (the older versions are creating
the network bridge).
In general, however, I would say the broker's aren't guaranteed to network
with each other between versions. The clients + openwi
Hi all,
on trying the latest ActiveMQ 5.8-SNAPSHOT broker, I get these errors, when
other brokers (older versions, but at least 5.6) try to make a duplex
connection.
2012-11-30 17:16:21,443 ERROR emq.broker.TransportConnection - Failed to
create responder end of duplex network bridge
VMware-564da
Yah, I agree. The best way would be to have it properly exposed and used
that way. Which is what JMX does. Or, as Gary mentioned in another post(
http://activemq.2283324.n4.nabble.com/ActiveMQ-Advisory-Connection-messages-includes-username-and-password-td2365496.html),
maybe we should just change
h
Awesome, thanks Gary!
On Fri, Nov 30, 2012 at 8:41 AM, Gary Tully wrote:
> use the destinationpolicy entry cursorMemoryHighWaterMark, it default to
> 70% of the system usage. so set it to something low like 2% and it will
> spool to disk very early.
>
> When reading back in from disk, it pages i
Christian,
Thanks for pointing me in the right direction. Here's my code that seems to
work so others can use it. That said, I'm really nervous about using
reflection to get at the brokerConnectionStates collection. There must be a
better way to do this...
@SuppressWarnings("unchecked")
use the destinationpolicy entry cursorMemoryHighWaterMark, it default to
70% of the system usage. so set it to something low like 2% and it will
spool to disk very early.
When reading back in from disk, it pages in messages in batches, this is
controlled by the maxPageSize policy enry for a desti
Hi,
the problem with 0 prefetch and Stomp is that there's no mechanism in
stomp to explicitly pull the message from the broker. You can only
subscriber and unsubscribe from the destination. I'm not aware of any
workaround.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource
Hi,
We experienced a loss of messages under critically high load conditions on
one of our brokers. Unfortunately, the high load caused us to lose the logs
of the small time window during which we lost messages. I am trying to
understand how this happened.
Our setup is a network of two brokers. Wh
