Hi,
I am running activemq 5.4.2 with JDK1.6.025 in Linux. There are two
brokers configured via network of brokers. Java client connects to brokers
using the following failover url:
failover:(tcp://broker1:61616,tcp://broker2:61616)?randomize=false&initialReconnectDelay=15000&maxReconnectAttem
On Thu, Nov 22, 2012 at 11:19 AM, Laurent Laborde wrote:
> Friendly greetings !
> i rewrote
> http://www.nobugs.org/blog/archives/2008/05/11/squawk-simple-queues-using-awk/
> The repository can be found here : https://github.com/ebuzzing/bash-mq
BTW... I want it to be "production-ready".
If you
Hi James,
there's a reference on the source page
http://stomp.fusesource.org/source.html
but you're right that site needs some update. I'll try to do it these days.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dej
Friendly greetings !
i rewrote
http://www.nobugs.org/blog/archives/2008/05/11/squawk-simple-queues-using-awk/
The repository can be found here : https://github.com/ebuzzing/bash-mq
Feature :
- login/password handling
- program option using getopts
- use socat instead of nc
- easier to maintain (h
I have a stomp client connected using pretty much default settings, and I
changed it to ack every 100 messages for performance.
It gets one message then gives up.
Checking the "Active Consumers" for the queue I two entries:
A client-id, with a prefetch of 1
A connection-id, with a prefetch of 0
Hi Tony,
As I mentioned in my previous email, this error is generally thrown if the port
(61618 in your example) is already in use by another process.
Stop your broker and run
netstat -an | grep 61618
and if you see something like this line being printed
tcp4 0 0 *.61618
