Hi Karl,
Thanks for your answer and the quick fix.
Best regards,
Olivier
> Le 13 mai 2019 à 19:46, Karl Wright a écrit :
>
> I committed a fix for this hang to trunk.
> Karl
>
>
> On Mon, May 13, 2019 at 11:40 AM Karl Wright wrote:
>
>> Thanks -- this shows a classic deadlock occurring,
I committed a fix for this hang to trunk.
Karl
On Mon, May 13, 2019 at 11:40 AM Karl Wright wrote:
> Thanks -- this shows a classic deadlock occurring, where the System.exit()
> call effectively blocks the thread that does it from exiting, and thus
> blocks the system from shutting down. This
Hi Karl,
Thank you for your mail.
I installed an ootb MCF 2.13 to have a clean installation. I launched the
File-based multiprocess example and I did the previous tests I mentioned.
I managed to see the error that you told me about :
agents process ran out of memory - shutting down
The thread dump is not helpful. I see no traces for any threads that
identify code from MCF at all. That's new and has nothing to do with MCF;
it's probably a new Java "feature".
The OutOfMemoryException should, I've confirmed, be rethrown. The Worker
Thread code does in fact catch the
Hi Olivier,
Any out-of-memory exception that makes it to the top level should cause the
agents process to shut itself down.
The reason for this is simple: in a multithread environment, with lots of
third-party jars, an out-of-memory in one thread is usually indicative of
an out-of-memory in
It sounds like there might be an out-of-memory situation, although if that
is the case I would expect that the MCF agents process would just shut
itself down.
If the process is hung, it should be easy to get a thread dump. That would
be the first step.
Some thoughts as to what might be
