Message size chokes the connection between Cloverleaf and Epic InterConnect

Every now and then we get very large message from an application and it seems to choke the connection between Cloverleaf and our Epic InterConnect thread. These message are usually larger than 10 mg.  We had one yesterday that was 17.1 mg and had over 4500 embedded PDF’s in the OBX segments. There is a translation on this feed. I found an old thread discussing increasing the size of memory, stack and processes. The results of running the ulimit -a returns the following:

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 1030675
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 65536
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

For the size and content of the message mentioned, should any of these be increased and what would the recommendation be? As always thanks in advance.