May be worth connecting to ActiveMQ to inspect it at the JMX level (hawt.io is an excellent interface). Check why ActiveMQ thinks it should not be delivering it.
On 21 January 2015 at 04:29, mvandersteen < mark.vanderst...@servicestream.com.au> wrote: > Hi Guys, > > I have 1 queue created through camel that holds onto messages for approx 15 > minute before a consumer will pick them up. > > A cxf web service listens for incoming message as SOAP, then pushes > translated message to said queue. > > That message will sit there for approx 15 minutes before another route will > pick it up for processing. We have approx 100 different queues across 25 > bundles or so and this is the only one I've seen this happen on. Which to > me > indicates some configuration somewhere. > > I've been developing camel for approx 18 months and not seen this behaviour > before either hence the question to you guys. I can't see anything obvious > in configuration files for the bundle or parameters being set for the jms > queue either. > > Could anyone please give me a few pointers on what might be happening here. > > Cheers > Mark > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Messages-sitting-on-ActiveMq-for-x-period-of-time-tp5761970.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
