Ticket #85 (closed defect: fixed)
Change ordering of memory settings on linux initscripts
|Reported by:||smith@…||Owned by:||smith@…|
I've been looking into an issue where raptormuad was failing to run,
logging an exception which ended in java.lang.OutOfMemoryError?: Java
This turned out to be because the server had an older Java version
(1.6.0 u4) and it was ignoring the -Xmx parameter.
Strictly speaking the heap size parameter, -Xmx, should come before
the jarfile option in the command line (java [-options] -jar jarfile
[args...]) although it looks like more recent versions are more
permissive (1.6.0 u20 appears to allow this).
So moving the -Xmx switch in /etc/init.d/raptormuad fixed this issue for me:
javaArgs="-DconfigurationFiles?=/opt/raptor/mua/conf/ -Xmx512M -jar
So for better compatibility this option needs moving for this and the
other start-up scripts.
(Raptor v1 on CentOS 5).
All the best,
- Component changed from Distribution - RPM to Raptor (Common)
- Status changed from new to closed
- Resolution set to fixed
- Status changed from closed to reopened
- Resolution fixed deleted