activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Smith <joesmithc...@yahoo.com>
Subject Re: Could not start connection when using jms.prefetchPolicy on failover protocol url
Date Fri, 16 Sep 2011 14:58:23 GMT
Hi Gary,

Yes, we saw in the debug logs that remote consumer and subscription are added to the local
broker.  We noticed the prefetch count was 1000, instead of 1 on the consumer's uri.  We
added the prefetchSize to the networkConnector, but still the same result.  When we use consumers
that consume messages quickly - the cluster load balanced evenly.  However, when we made
the processing from 1 to 20 secs (via a parameter in each message), the broker where the producer
is connected and when the consumer on that broker was busy already, the broker seems to directed
the message to the other brokers - even if the consumers on the other brokers were busy/processing
as well.

Really appreciate you and all the folks who are helping.  Hope some of this feedback will
help.

Thanks


________________________________
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org; Joe Smith <joesmithcomm@yahoo.com>
Sent: Friday, September 16, 2011 5:56 AM
Subject: Re: Could not start connection when using jms.prefetchPolicy on failover protocol
url

note that there is a perfetch configuration option on a networkConnector.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message