Thanks. I missed that property :-)
On Tue, Jul 8, 2014 at 7:15 PM, Claus Ibsen-2 [via Camel] <
ml-node+s465427n5753556...@n5.nabble.com> wrote:
> Hi
>
> See the acceptMessagesWhileStopping option on camel-jms component
>
> On Tue, Jul 8, 2014 at 12:47 PM, Paolo28 <[hidd
Hi,
I would like to understand more how Camel handles messages during shutdown.
In my app. I have just single route which is connected to IBM Websphere and
processes given queue.
One thing we did not fully understand is what is actually happening when
consuming the queue in TRANSACTED mode and wh
Yes but for me resource pooling/caching and resource cleanup are two
different things. If I did not use Camel but plain Java I would not face
this issue even with MQQueueConnectionFactory (no wrappers) ...
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-memory-leak
Conclusion:
I have solved the issue few days ago by using Spring
CachingConnectionFactory which wraps MQQueueConnectionFactory - I was aware
of this possibility but I could not believe it can create memory leak. I
still don´t understand it and IMO this is bug (MQ?).
--
View this message in c
Hi,
I use IBM MQ not ActiveMQ but I considered wrapping MQ conn. factory with
Spring impl. but anyway caching is always about performance boosts so the
calling code does not create expensive objects over and over if not needed.
However if not caching it should not result in memory leak. Resoruces
Hi all
In my simple application I have following flow:
1. connect to MQ Queue Manager
2. consume messages via jms component in multithreaded mode (5-8 threads)
AND transacted mode
I´m using standard external Spring JmsTransactionManager which operates
on MQQueueConnectionFactory.
3. proces th
Hi,
I´m not calling web service. In my case I had just file poller, splitter
with streaming (line by line processing using Camel Bindy), then aggregator
with parallelProcessing set true. Basically very simple flow. I wanted to
see the threads using JVVM but the JVM connection attempt always resulte
I have the same problem.
I have not found any solution to this issue. I believe that Camel should be
able to shutdown itself in a graceful manner. My scenario:
1. process N messages (I´m able to detect which is the last)
2. once all messages are processed I want to gracefuly terminate the process
