0

We've started to get some intermittent critical errors on our production node that's forcing us to restart the node. I believe that the errors are related to adding images to memory before they are uploaded to the server. The first few lines of the stack trace are as follows: Jul 19 13:48:52.627 - CRITICAL - M2EE: An unhandled error occurred in the MxRuntime. Jul 19 13:48:52.628 - CRITICAL - M2EE: (1/33) java.lang.OutOfMemoryError: Java heap space Jul 19 13:48:52.628 - CRITICAL - M2EE: (2/33) #011at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75) Jul 19 13:48:52.628 - CRITICAL - M2EE: (3/33) #011at java.awt.image.Raster.createPackedRaster(Raster.java:467) Jul 19 13:48:52.628 - CRITICAL - M2EE: (4/33) #011at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032) I've googled java.awt.image.DataBufferInt outofmemoryerror and this post on Stack Overflow indicates that the problem is down to corrupt images and how they are handled (or not). The problem is that I have no idea how to recreate this, or how to handle this specific out of memory error so that the application fails gracefully rather than grinding to a halt. Does anyone out there have any insight?

asked 2017-07-25

1 answers