Using activemq 5.4.0 for a P2P desktop applicaiton, I get an OOME when
my computer awakes from sleep:
Exception in thread "InactivityMonitor WriteCheck"
java.lang.OutOfMemoryError: unable to create new native thread
The cause appears to be:
- WRITE_CHECK_TIMER schedules checks at a fixed rate
I'm using a peer-to-peer connection with MulticastDiscoveryAgent. Each
instance listens to a topic, and then some instances publish messages to
that topic.
When a new instance starts up, there's a roughly 20 second lag between
when it joins the network and when it starts to receive messages s
On 10/26/2010 4:24 AM, Gary Tully wrote:
That looks like a bug in the peer transport factory. I uses
localhost:0 as the tcp transport url, but localhost maps to the
loopback address since 5.3[1] so the connection is refused.
The peer transport factory should use the wildcard address, 0.0.0.0
Fo
I'm trying to implement broker discovery using ActiveMQ 5.4.0. I've
been successful using multiple JVMs on one host, but I'm unable to set
up a network between hosts.
My simplest attempt has been to use the peer: transport. The UDP
messages passed have the contents:
redgroup.ActiveMQ-4
