Hi I have a MapServer service whose arcsoc crashes due to not enough java heap space. This happens when a /query request is made for all features, geometry, and attributes and the return format is pjson. The max records returned for the service is the default 2000.
I have found that if I set the javaHeapSize for the service to 312 (MB) that the query will be processed by the service and data begins to download.
If in addition orderByFields are specified in the query, I have to increase the javaHeapSize value to 1024 (MB).
I only have a max of two instances for this service so increasing the javaHeapSize to 1024 still appears to keep memory utilization for the machine in a healthy zone. It doesn't appear that the entire 1024 MB are used right away; just perhaps that the arcsoc has more "headspace" to execute larger queries.
I'm wondering if others have had to increase the javaHeapSize beyond the 64MB default. Who can report the biggest, baddest javaHeapSize of them all??
Tim
