Hello,
I'm experiencing a problem getting AMQ 5.4 to run with UDP transport.
Basically, what happens is that the
broker completely ignores the UDP port number that is specified in the
configuration (e.g., uri="udp://localhost:8123")
and listens on a seemingly random port number, as reported by
I'm confused.
"KahaDB is a file based persistence database that is local to the message
broker that is using it. It has been optimised for fast persistence and is
the the default storage mechanism from ActiveMQ 5.4 onwards." --
http://activemq.apache.org/kahadb.html
So I assume KahaDB is suppor
hi,
Our system uses activemq5.3.0, running about 15 days, monitoring to two
messages can not be consumed, only behind the message into the queue, before
the backlog of messages to be consumed, the queue still retains two new
messages can not be consumed in the queuećOnly after the application res
We have the following situation:
Client DMZ Server
Amq --->SSL > Proxy -> TCP --->Amq
Can activemq work in this situation to example failover,check consumer
Can you please say me if it's work or not? Thanks im be
"lernen.2007"
writes:
> I want if there is no space to persistence messages that activemq remove all
> messages. How can I do that?
Umm... make the messages non persistant? Because that is the only
difference between them ;)
Ok, I think it's a problem that is signaled with Topic and
conduitSubscriptions set to false (what I need for selectors and queue load
balancing)
I think it's the A's embedded broker which sees 2 consumers on B's broker
and decides to send 2 messages because conduitSubscription is false.
It's st
Hi
With 5.4.2.
I have 3 Java processes
A : embedded broker in a process that contains a producer and a consumer on
a topic
B : embedded broker in a process that contains a consumer on this topic
C : process that contains a consumer on this topic
C is connected (TCP) on B's embedded broker
B's
