A Gateway Compression Error is typically encountered in the logs, with a message indicating a "compression failed error" followed by random, mostly fatal errors:
When you see the 'compression failed' error messages then the most likely cause is that the gateway has run out of memory, and the gateway has crashed and created a core dump.
There have also been numerous memory leak fixes over the several release versions, particularly starting with GA3.0.16. If you frequently encounter this error and is already running the latest production version of the Gateway, it is recommended that you track and chart the gateway memory usage over time and find out when it's increasing.
A quick note when monitoring memory usage, in particular the Resident Set Size may not be that useful in this exercise (Resident Set Size being the amount of memory in physical RAM rather than the total memory a process is using, so if a process doesn't use a piece of memory for a while then the OS may put it onto disk to free up the RAM and that number would go down even though the process is still using it. If memory has leaked then there's no possibility that we'll ever access it again so there's much more chance that the OS will swap it into disk) - It's more useful to chart Virtual Memory in this case.