Thanks! Problem fixed. In fact, another consumer was geting the messages before the expected consumer.
tranchida wrote: > > It's look like a problem with the prefetch on activemq > > http://activemq.apache.org/what-is-the-prefetch-limit-for.html > > Try to add tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=0 (or 1) > > or > > add a PooledConnectionFactoryBean around your ActiveMQConnectionFactory > > > jcamus wrote: >> >> Hi! >> >> I am trying the following architecture : >> >> filePoller -> JMSProvider -> JMSConsumer -> Bean-Se >> (in directory) (concurrentConsumers=5) >> I want to limit the number of threads processed at the same time (for >> example if I have many >> files sent in the directory) so I set the concurrentConsumers=5 to the >> JMS consumer. >> Unfortunately I saw that some files processed are lost (and never >> received by the Bean-se) ! >> >> Why? >> >> If I remove concurrentConsumers it works fine but I can't limit the >> number of threads used. >> Can you help me? >> >> Regards. >> >> >> > > -- View this message in context: http://old.nabble.com/JMS-%3A-message-lost--tp27112810p27160506.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
