Following recent advice, I set up my endpoint to enable two threads
via JMS config, and left the executor alone.

I then found myself with a memory leak which can only be explained if
these threads are being created and destroyed fairly often, rather
than just hanging around.

Does this seem possible? If so, any ideas for how to get some code to
run on the way out?

Reply via email to