[Geoserver-users] Can GeoServer corrupt a shapefile .dbf ?

Hi list,

Using 1.5.1. Something strange happened. I had a shapefile in a geoserver-only folder which was served by GeoServer. When trying to restart GeoServer this morning, I found out GeoServer could not serve the shapefile anymore and when trying to load it anew, GeoServer told me the .dbf is corrupted. It's true, the .dbf has been changed. No app other than GeoServer accessed the shapefile which has been corrupted, that's why I suspect GeoServer itself induced the corruption?!

Files are attached in the GEOS-1218 bug report (which may be another bug unrelated to the corruption problem). As I said in the bug report, I received the shapefile in question from someone else, so I'm not sure if the shapefile itself is ok (but it should be since no other app had any problem with it).

Have a nice Monday :slight_smile:

Alex
--
Alexandre Leroux, M.Sc., Ing.
Environnement Canada / Environment Canada
Centre météorologique canadien / Canadian Meteorological Centre
Division de la réponse aux urgences environnementales /
Environmental Emergency Response Division
alexandre.leroux@anonymised.com

Alexandre Leroux ha scritto:

Hi list,

Using 1.5.1. Something strange happened. I had a shapefile in a geoserver-only folder which was served by GeoServer. When trying to restart GeoServer this morning, I found out GeoServer could not serve the shapefile anymore and when trying to load it anew, GeoServer told me the .dbf is corrupted. It's true, the .dbf has been changed. No app other than GeoServer accessed the shapefile which has been corrupted, that's why I suspect GeoServer itself induced the corruption?!

Hmm... this should hardly happen unless someone did a WFS-T transaction
against the file that failed mid-way.
I'll have a look at the file.

Cheers
Andrea