I will give it a try later, but it seems to me that it probably won't solve the problem since the consumer fetches the message as soon as it is published, and when I increase the message size, the number of message that can be send decrease accordingly. For example, when the BytesMessage has the payload doubled, the number of BytesMessages that were send almost halved (but not exactly).
bsnyder wrote: > > Most typically this is an issue with the consumer side processing > being much slower than the broker side, so the messages back up on the > broker. One solution to such slow consumer situations is to use the > consumer prefetch prefetch policy. See the following for more info: > > http://activemq.apache.org/what-is-the-prefetch-limit-for.html > > Please read through that and see if it describes your situation and if > it does, give the prefetch policy a try. > > Bruce > -- > perl -e 'print > unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" > );' > > Apache ActiveMQ - http://activemq.org/ > Apache Camel - http://activemq.org/camel/ > Apache ServiceMix - http://servicemix.org/ > Apache Geronimo - http://geronimo.apache.org/ > > Blog: http://bruceblog.org/ > > -- View this message in context: http://www.nabble.com/Publisher-can%27t-publish-after-a-certain-number-of-messages-are-sent-tp16995039s2354p17023458.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
