It doesnt (usually) matter how big the dataset is, just how big the
Can you send a typical WMS request that causes this problem? Do you know
what size of data you are requesting? What file format?
-Xmx1536m is around the max for 32 bit JVMs. I strongly advise you to
use a 64bit JVM with more like 4 Gbyte heap.
On 3/29/2011 7:19 PM, Xiangtan.Lin@xxxxxxxx wrote:
I'm in process of serving out some large aggregated datasets (5 -
8GB) with Thredds WMS. I consistently experience "OutOfMemoryError:
Java heap space" error when making WMS requests. On my test machine,
I've allocated -Xmx1536m to Tomcat and experimentally Thredds is able
to serve about 1GB aggregated datasets.
By digging through the Dataset Aggregation and Memory related topics
on the list, I've found out that the general suggestions are to
allocate more memory to Tomcat such as: -Xmx4g
One post mentioned that "Thredds does everything in memory".
Can somebody please advise how much memory I should allocate to
Tomcat for the 8GB dataset? I'm afraid I have to secure more than 8GB
And what is the best practice to serve out the large datasets on
Thredds in general?
Regards and thanks,
Technical Services Officer *|*CSIRO IM&T
thredds mailing list
For list information or to unsubscribe, visit: