Re: Network bridge throughput capped at default Socket buffer size

Hi Tim, Here are the OS config: *Broker A* $ cat /proc/sys/net/ipv4/tcp_rmem 409687380 16777216 $ cat /proc/sys/net/ipv4/tcp_wmem 409687380 16777216 *Broker B* $ cat /proc/sys/net/ipv4/tcp_rmem 409687380 16777216 $ cat /proc/sys/net/ipv4/tcp_wmem 409687380 16777216 As in

Re: Network bridge throughput capped at default Socket buffer size

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://acti

Network bridge throughput capped at default Socket buffer size

d 1:1 Best regards, Leung Wang Hei -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-bridge-throughput-capped-at-default-Socket-buffer-size-tp4696643.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Forward activemq log to a topic on itself via Log4J JMS appender

We have a tool to hook to a well-known topics to receive logging from all applications. Now we would like to reuse this topic to monitor some special logging (e.g. network bridge down) of ActiveMQ itself. Enabling jms appender in log4j.properties (see below) always causes start up error: *log4

Re: 回覆︰ Static network connector with message selector

Anyone else encountered the same problem? -- View this message in context: http://activemq.2283324.n4.nabble.com/Static-network-connector-with-message-selector-tp4664389p4664657.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.