Tim,
I have used "transport.socketBufferSize=x" in transport connector broker A
and only "?socketBufferSize=x" in broker B network connector. When x=-1,
warning is raised in MQ log:
/[WARN ] org.apache.activemq.network.DiscoveryNetworkConnector - Could not
start network bridge between:
vm://activemq.auhkmq01?async=false&network=true and:
tcp://brokerA:61616?socketBufferSize=-1 due to:
java.lang.IllegalArgumentException: invalid receive size/
If I prefix broker B config with "transport.", the parameter is considered
invalid by MQ:
/[WARN ] org.apache.activemq.network.DiscoveryNetworkConnector - Could not
connect to remote URI: tcp://brokerA:61616?transport.socketBufferSize=-1:
Invalid connect parameters: {transport.socketBufferSize=-1}/
It looks like my initial config is correct.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Network-bridge-throughput-capped-at-default-Socket-buffer-size-tp4696643p4696748.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
