On 12/06/2013 11:52 AM, gmotts wrote:
I have a general question regarding ActiveMQ Advisory Topics. By default
ActiveMQ records basic events such as starting and stopping consumers,
producers, and connections for the broker.. I'd like to understand what is
the overhead associated with this beh
I have a general question regarding ActiveMQ Advisory Topics. By default
ActiveMQ records basic events such as starting and stopping consumers,
producers, and connections for the broker.. I'd like to understand what is
the overhead associated with this behavior when AMQ is running for a long
per
I hava on topic with a lot of producers and 1 durable subscribe consumer.
activemq conneted to mysql with c3p0 datasoure pool with the default
configuration. The jdbcPersistenceAdapter cleanupPeriod is 3000。 when all
producers commit message, sometimes activemq blocked, no message can send or
r
We have 4 clients publishing to a virtual-topic, and 4 instances of an
application with 15 consumers consuming messages from that topic.
The topic is running on two servers (A and B) with a duplex networkconencts
from A to B.
Thw transportConnector is set up with setUpdateClusterClientsOnRemove an
Pure master/slave is departed in later releases and wont get supported any
more.
You should consider other cluster topology.
2013/12/3 赵振华 ZhenhuaZhao
> hi,all
> I’m a newbie in activemq.
>I use active-5.5.5 on rhel5.4 X86_64 in pure master/slave mode.
> I leave master’s config