Re: java.lang.OutOfMemoryError: allocLargeObjectOrArray

Good morning,

we spend late yesterday and this morning again a lot of time on this issue.
It seems that we have a dependency between memory usage and tmp$-Queues.
It seems that the tmp-Queues created are allocating memory which could not be Garbage collected, and so JVM run's to an OOM. After giving JVM 512 MB more Heap it was just a question of time until the heap was completely used again. We see no possible GC's on old Gen and that Survivor was empty, seems no space avaliable. This seems to be the same behavior allways when OOM happens.

The tmp-Queues and the allocated memory are not released after restart of router, only when we move db/transactions and start "empty".

In which cases a tmp-Queue is created and not released (in 4.5.1.)? Please see also screenshot for Queue config. Would it make sense and help to change to persitent?

Thanks,
Michael