peek at producer flow control - http://activemq.apache.org/producer-flow-control.html
configure brokerB with the default store cursor that will stop caching messages rather than retain messages in memory. On 24 June 2014 10:42, multani <multani1...@gmail.com> wrote: > Hi all, > > I set up two activemq servers A, B. Server A will use network connector to > push all messages it receives to server B. The configuration is like this: > > <networkConnectors > xmlns:spring="http://www.springframework.org/schema/beans";> > <spring:bean id="ycaNetworkConnector1"> > <spring:constructor-arg value="conn1" /> > <spring:property name="uri"> > > <spring:value>static:(tcp://serverB:61616,tcp://serverB-bcp:61616)</spring:value> > </spring:property> > <spring:property name="name"> > <spring:value>conn1</spring:value> > </spring:property> > <spring:property name="networkTTL"> > <spring:value>3</spring:value> > </spring:property> > <spring:property name="staticallyIncludedDestinations"> > <spring:list> > <spring:bean > class="org.apache.activemq.command.ActiveMQQueue"> > <spring:constructor-arg value=">"/> > </spring:bean> > > </spring:list> > </spring:property> > </spring:bean> > </networkConnectors> > > This configuration works fine buy when there too many messages in server B. > Messages received by server A pushes messages very slow and messages are > stuck in server A. > > Does anyone know why this happens and how to avoid it? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Why-does-network-connector-slow-down-when-there-are-too-many-messages-in-downstream-broker-tp4682411.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
