Prefetch <http://activemq.apache.org/what-is-the-prefetch-limit-for.html> is the problem with pooling consumers. A consumers pre-fetched messages, when that consumer is in a pool, may stay there till the pool is closed and will not be available to other consumers.
2009/3/20 ashoknan <ashokkumar.sanka...@chase.com> > > Am i not supposed to use PooledConnectionFactory for consuming messages.See > the below Java Doc > > http://activemq.apache.org/maven/act...onFactory.html > > > A JMS provider which pools Connection, Session and MessageProducer > instances > so it can be used with tools like Spring's JmsTemplate. NOTE this > implementation is only intended for use when sending messages. It does not > deal with pooling of consumers; for that look at a library like Jencks such > as in this example > I am not sure whether this is outdated. > > Please let me know if anyone faced this issue before > -- > View this message in context: > http://www.nabble.com/ActiveMQ-producer-consumer-hangs-when-on-of-the-consumer-didn%27t-respond-tp22586789p22614510.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com
