I upgrade the CentOS form 6.0 to 6.2, the high CPU issue is gone.
I think the KahaPersistenceAdapter default already include the share file
lock, we don't need to define it, isn't it?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-7-master-salve-nfs4-both-a
I see. I didn't realize you were using the old deprecated
KahaPersistenceAdapter.
On Fri, Jul 19, 2013 at 2:43 PM, zhjt80 wrote:
> I upgrade the CentOS form 6.0 to 6.2, the high CPU issue is gone.
>
> I think the KahaPersistenceAdapter default already include the share file
> lock, we don't need
Thanks for the reply. We've tested both settings and we have the following
concerns. We would like to have a HA setting using master/slave and we want
to find out how to setup HA mysql database correctly. Please advise.
1) For Federated network of brokers, only one broker will persist messages
Am 19.07.2013 00:49, schrieb slam:
Hi Christian,
In your multi master MySql setup, did you replicate the data? If not, will
you lose messages if one of the MySql servers that contains messages
failed/shut down?
assuming you did refer to me.
I do not run MySQL replication, like Master-Master
I have two brokers set up on two servers. One is 10.194.2.1, the other
is 10.194.2.2 .
One of them has this in its config file:
uri="static:(tcp://10.194.2.1:3000)"
duplex="true" />
I have clients connecting
peek at
https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/MessageListenerRedeliveryTest.java#L318
On 18 July 2013 06:50, Tushar Nagar wrote:
> Hi,
>
> I hv been trying this but was unable to find it anywhere. I hv a scenario
> where I hv a queue
The most widely used protocol (and most mature one) is definitely OpenWire
over the TCP transport.
Discovery tends to be very customer-specific, depending on what your IT
infrastructure department accepts, e.g. multicast may be disabled on your
network, in which case you could use Fabric or LDAP,
