Re: Network Connector too slow when receive high rate persistent message

I tried to set with your suggestion as below, however, performance is still slow. Fortunately, I found another ways to improve that set journalDiskSyncStrategy="periodic" and clear the /data before start ActiveMQ. The performance can go to 1,000 msg/s with 2K message size. Second way, use SSD

Re: Network Connector too slow when receive high rate persistent message

I used default Kaha DB and run with HDD disk under Linux O/S. -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-Connector-too-slow-when-receive-high-rate-persistent-message-tp4721293p4721317.html Sent from the ActiveMQ - User mailing list

Network Connector too slow when receive high rate persistent message

I have set up ActiveMQ 5.14.3 cluster (2 Brokers) with using Network Connector. I tried to send 4,000 persistent message to a queue in 300 msg/sec rate. The Producer can send same rate (300m/s) with using "useAsyncSend=true", however, consumer just can receive all messages in *40 msg/sec* rate.

Redelivery & DLQ setting not work

I am using ActiveMQ 5.14.3 with setting redelivery policy and DLQ. However, whatever I set the value in maximumRedeliveries and DLQ, ActiveMQ always use default value instead. Please help. *ActiveMQ Configuration* http://activemq.apache.org/schema/core; brokerName="ADSR.Broker1"

Cannot sync message that return back to JMS server when client does not acknowledge

I have set up JMS Cluster with ActiveMQ v5.14.3, set up network connector and enable duplex as below. Also, a JMS client (Client Acknowledgement) can receive queue message from both JMS servers but not send acknowledgement for the message. When I terminate the client, the unacknowledged messages