GeoServer

WCS runs out of memory

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 2.0.0
  • Fix Version/s: None
  • Component/s: WCS
  • Labels:
    None
  • Environment:
    Windows server 2003, JDK 1.6.06
  • Number of attachments :
    2

Description

I have a huge imagemosaic (45000 png files with 45000 worldfiles) and a shapefile with the index for all these files. If I request:
localhost:8080/geoserver/ows?service=WCS&request=GetCoverage&format=png&version=1.0.0&&coverage=geodan:SwisstopoVec200R&resx=1&resy=1&crs=EPSG:3035&BBOX=4210298.73562557,2695385.2900159317,4210649.130299931,2695865.828956959
It should produce a PNG file of 350x480. Instead it crashes with an OutOfMemoryError. The same request on the sameserver with the same data but Geoserver 1.7.6 does work (albeit with a memoryleak).

I've included the commandline output of Geoserver from startup to crash. And I had -XX:-HeapDumpOnOutOfMemoryError added to the startup command.

  1. Text File
    stacktrace.txt
    27/Oct/09 11:32 AM
    43 kB
    Steven M. Ottens
  2. Text File
    stacktrace2.txt
    20/Nov/09 6:35 AM
    33 kB
    Steven M. Ottens

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

As far as I know WCS does not use overviews to provide the max accuracy, which mean it will load all of the original image. If the original image is not properly tiled (tiled geotiff) this will definitely result in a OOM if the file is big.

Unfortunately I don't know about too many details to comment intelligently on this one, but I've cc'ed Simone and Alessio that surely know the code better than me

Show
Andrea Aime added a comment - As far as I know WCS does not use overviews to provide the max accuracy, which mean it will load all of the original image. If the original image is not properly tiled (tiled geotiff) this will definitely result in a OOM if the file is big. Unfortunately I don't know about too many details to comment intelligently on this one, but I've cc'ed Simone and Alessio that surely know the code better than me
Hide
Permalink
Steven M. Ottens added a comment -

Just to give an idea of the file sizes involved:
The tiles are 1500x1500 pixels and the request I did fits within a tile, so in theory it should at max need 4 tiles. As PNGs they are about 30Kb but as uncompressed tiled GeoTIFF they're around 300MB.

Show
Steven M. Ottens added a comment - Just to give an idea of the file sizes involved: The tiles are 1500x1500 pixels and the request I did fits within a tile, so in theory it should at max need 4 tiles. As PNGs they are about 30Kb but as uncompressed tiled GeoTIFF they're around 300MB .
Hide
Permalink
Steven M. Ottens added a comment -

I've moved Geoserver to a 64bit linux machine (it was a 32bit windows) now the above request works. However when a lot of requests are coming in I still get an OoM-error. I've noticed GEOS-3660 so to be sure that is not causing the problem I've upgraded Geoserver to the latest nightly.
I've attached a new logfile with debugging switched on. (stacktrace2.txt)

Show
Steven M. Ottens added a comment - I've moved Geoserver to a 64bit linux machine (it was a 32bit windows) now the above request works. However when a lot of requests are coming in I still get an OoM-error. I've noticed GEOS-3660 so to be sure that is not causing the problem I've upgraded Geoserver to the latest nightly. I've attached a new logfile with debugging switched on. (stacktrace2.txt)
Hide
Permalink
Steven M. Ottens added a comment -

Log file with verbose logging on

Show
Steven M. Ottens added a comment - Log file with verbose logging on
Hide
Permalink
Simone Giannecchini added a comment -

Improved WCS code on trunk, please test a nightly

http://gridlock.openplans.org/geoserver/trunk/

Show
Simone Giannecchini added a comment - Improved WCS code on trunk, please test a nightly http://gridlock.openplans.org/geoserver/trunk/
Hide
Permalink
Steven M. Ottens added a comment -

Geoserver has been running stable for a long time now. There has been some minor adjustments to the services which generate requests, mainly in reducing the requested image to sub 7000x7000pixel sizes.

Show
Steven M. Ottens added a comment - Geoserver has been running stable for a long time now. There has been some minor adjustments to the services which generate requests, mainly in reducing the requested image to sub 7000x7000pixel sizes.

People

  • Assignee:
    Simone Giannecchini
    Reporter:
    Steven M. Ottens
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: