Opened 11 years ago

Closed 11 years ago

#187 closed defect (fixed)

1.2.0 Beta 2, GDAL and Tiling Service crashes

Reported by: amorsell Owned by:
Priority: high Milestone: 2.0
Component: Server Version: 1.2.0
Severity: major Keywords:
Cc: warmerdam External ID: 943485

Description

I am using the GDAL provider in 1.2.0 beta 2 to access a directory of about 850 ECW images. Each image is about 25 MB and there is a total of 20 GB in the directory. Creating a layer with a zoom threshold of 1:50,000 actually works pretty well, but is still too slow due to the GDAL provider's lack of tile indexing. We would like to use base layer tiles instead. But, upon initial tests this locks up the MG server service. This is easily replicated after restarting the service. The log file returns an error like:

<2007-05-31T19:17:10> Anonymous

Error: Failed to stylize layer: Austin_2006_aerials_ECW

An unclassified exception occurred.

StackTrace?:

An unclassified exception occurred.

This happens both with the service running normally and in interactive mode. Interactive mode does not yield any meaningful messages. The mgserver.exe process is still resident in addition to four MapAgent?.exe processes. If I look at the tile folders, the folders have been created, but only one PNG actually created in one folder (R0/C0 folder). However, there are four .lck files in that folder. All have the same time stamp and are 0 KB in size.

I even tried this with just two images and upon succesive zooms to force tiles to create at the various zoom factors, I can readily crash the server.

Change History (6)

comment:1 Changed 11 years ago by tomfukushima

Milestone: 1.3

Will not be fixed in 1.2.0. Moving to 1.3.

comment:2 Changed 11 years ago by amorsell

Some additional information from error.log

<2007-06-01T19:35:30> Anonymous

Error: An unclassified exception occurred. StackTrace?:

<2007-06-01T19:35:35> Administrator

Error: An unclassified exception occurred. StackTrace?:

comment:3 Changed 11 years ago by rexszeto

External ID: 943485

comment:4 Changed 11 years ago by warmerdam

Andy,

I wonder if this is related to the GDAL multi-threading issue:

http://trac.osgeo.org/fdo/ticket/100

comment:5 Changed 11 years ago by warmerdam

Cc: warmerdam added

comment:6 Changed 11 years ago by jbirch

Resolution: fixed
Status: newclosed

Closing, stability of GDAL provider was improved drastically with 1.2 Release. Ongoing issues with raster provider should be logged against FDO.

Note: See TracTickets for help on using tickets.