My activemq.xml is configured like below.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/java-io-EOFException-when-ActiveMQ-starts-tp4717598p4717709.html
Sent from the ActiveMQ - User mailing list archive
Can you please forward the details of how you're mounting the NetApp
exports? Please include all all NFS parameters.
Thanks,
Paul
On Thursday, October 6, 2016, fg wrote:
> Hi,
>
> We have 5 managed virtual servers with managed NetApp SAN Storage at our
> hoster. On
The first thing I notice is that you haven't actually enabled failover. The
connection URI should be based on this:
activemq:failover:tcp://hostname:61616
The inclusion of failover: is important.
Beyond that, if you break inside of a debugger, you most likely will be
disconnected by the broker.
Hello all,
As we prepare to ship our new product that uses ActiveMQ NMS heavily, I am
trying to harden the code against possible failures. One of the things that
our developers have noticed (and others in this group may have noticed) is
that it is common to get NMSExceptions when you are stopped
Hello,
On both the client and the server (where broker is started) I am seeing an
udp port being opened.
The port number is random each time. I am not figuring out why this udp port
is being opened or which static code is opening it.
Wondering whether anyone can throw some light on why this udp
This blog post (
http://workingwithqueues.blogspot.com/2012/05/activemq-virtual-topics-or-virtual.html?m=1)
seems to indicate that you can. Please let us know if it works.
On Oct 4, 2016 8:31 AM, "Devlin" wrote:
> When customizing virtual topic consumer "prefix", can
This is the first I'd heard of a replicated KahaDB implementation. I'd
heard of multi-KahaDB (mKahaDB), but that's multiple KahaDB databases on a
single broker (split by destination) rather than replicated. Maybe someone
else can provide more info...
On Oct 5, 2016 1:51 AM, "mlange"