Hi,
On 04/26/2017 07:58 PM, Jerry Malcolm wrote:
I've decided to take this in steps. My first objective is to just
kill the email the first time it causes an OOM and at least stop it
from going into an infinite loop trying to re-process it. My plan is
to modify SetMimeHeader.java and add to
I've decided to take this in steps. My first objective is to just kill
the email the first time it causes an OOM and at least stop it from
going into an infinite loop trying to re-process it. My plan is to
modify SetMimeHeader.java and add to to catch block. But I need help on
what I can do
Benoit,
Thanks so much for the information. This has definitely been a
frustration. I'm glad that there is some hope at getting around it.
You mentioned a SizeGreaterThan matcher. Two questions
1) How can I determine the threshold/limit size? I don't want to kill
off good emails
Hi,
You are processing a too large email. SetMimeHeader mailet is modifying
your email, but fails allocating more resources.
This may be caused to a missing pre-allocation parameter in
ByteArrayOutputStream. This sounds from the stacktrace like a limitation
of the javax implementation. (You
I have James R3B5. It's been working fine for over 2 years. But in the
last few months I randomly start getting repeated OutOfMemory
exceptions. The only fix I've found is to delete the var folder and
reboot. The OOM entry in the log is always preceded by an error related
to one
