We are considering ActiveMQ for production and somebody pointed to us the
following link. Anyone comment on the issues pointed out here ?
http://goodstuff.im/activemq-not-ready-for-prime-time
Thank you
Ravi
Hello,
I'm trying to setup a "network of brokers". In our dev and staging
environment I'm setting up two ActiveMQ servers, but in production there
will be at least four.
What I'm finding problematic is this...
The producer pushes messages to Broker1. If there are no consumers on
Broker1, the m
Hi,
I tried logging and various approaches. I even deleted all queues,
shut down cleanly via JMX, restarted several times. Except a long
startup for checksumming and verifying the logs, only checkpoint
entries. I even deleted the metadata store in order to force recovery
from the logfile, but stil
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
I seem to be losing some messages in a network of brokers topology in the
following setup:
- 1 producer pushing messages to a persistent queue (let’s call it
“IN.QUEUE.Broker1”) on one broker (broker1) inside a transaction. Producer
commits in every 100 messages.
- IN.QUEUE is a composite queue w
Hi
issues with a possible memory leak in ActiveMQ 5.5.0.
I've decided to open a new thread but this relates to my previous problem
here:
http://activemq.2283324.n4.nabble.com/Transaction-not-started-XA-problems-td3565540.html
The issue we are seeing is that ActiveMQ (broker) is holding onto mem
We have the problem that only after a failover the messages stuck. We use the
activemq version 5.5.0 and the same problem do we have in version 5.4.2 too.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/After-failover-some-messages-are-stuck-in-the-new-broker-tp3588033p3588
Hi,
I set the following configuration so that not messages stuck:
networkConnector
uri="static://(failover://(ssl://test:61616))?maxReconnectDelay=5000"
networkTTL="10"
dynamicOnly="true"
prefetchSize="1"
name="outbox
That's great. Cheers James.
Ozan
-Original Message-
From: James Green [mailto:james.mk.gr...@gmail.com]
Sent: 10 June 2011 09:21
To: users@activemq.apache.org
Subject: Re: Kahadb Corruption Scenarios
http://fusesource.com/docs/broker/5.4/persistence/KahaDB-Recovery.html
Don't forget the
http://fusesource.com/docs/broker/5.4/persistence/KahaDB-Recovery.html
Don't forget there are hardware-level performance improvements from the
operating system down to the disks which may affect reliability.
James
On 8 June 2011 16:53, Ozan Seymen wrote:
> Hi all,
>
> Can you please explain th
Hi All,
We are using apache-activemq-5.4.2 in jboss to acheive failover scenario.
Fail over scenario is working fine.
Current Cinfiguration :
in broker-config.xml
URI thro Code :
url="failover:(tcp://10.128.16.51:61616,tcp://10.128.16.57:61616)"
Now I like to bring the discovery feature
Hi Jydev,
Did you resolved this issue. I am also fasing the same issue. I am using
activemq 5.4.2. The messages are temporarily stuck for around 20 40
seconds.after that it consumes.When we browse from jmx console then also it
get consumed. any idea
Thanks
Krishnadasan T S
--
View this message i
12 matches
Mail list logo