[Geoserver-users] GS 1.6b4 crashing on new Featuretype

GeoServer GeoServer User
1

here's the shapefile:
      ftp://data.massgis.state.ma.us/pub/e00/state/trains_cov.exe

unzip it, and import the TRAINS_RTE_TRAIN.shp into postgis with the
following:
      shp2pgsql -d -I -s 26986 TRAINS_RTE_TRAIN.shp train_rte | psql
MY_GS_DB

then go into geoserver and try to make a new FeatureType out of this layer,
and get the following:
     GeoServer - Exception
     The following exception was thrown:
     java.lang.NullPointerException

with errors logged as such:
     http://transit.frumin.net/alewife/trains_rte.gsbug.txt

this is a first for a real GS crash for me. which means you guys rule!

-mike

PS I promise, I wont submit any more bugs to the mailing list before I file
the JIRA ones I owe you.
--
View this message in context: http://www.nabble.com/GS-1.6b4-crashing-on-new-Featuretype-tf4734933.html#a13540294
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

Hi Mike,

I grabbed ftp://data.massgis.state.ma.us/pub/shape/state/trains_shp.exe
and was able to reproduce the problem. The issue is that shp2pgsql is
creating the 'XYM' version of the geometry, and the postgis datastore
cannot handle that.

I am not sure if it is something with the source data that is causing
this or just something that occurs with newer version of shp2pgsql.

Anyways, I am opening a jira for this, as we should probably handle this
case, even if we just treat it like the XY case. I think that all we
need to do is handle geometry names that end in "M".

http://jira.codehaus.org/browse/GEOS-1465

If you want a quick fix just use the "-w" flag with shp2pgsql and it
should work like a dream.

-Justin

mfrumin wrote:

here's the shapefile:
      ftp://data.massgis.state.ma.us/pub/e00/state/trains_cov.exe

unzip it, and import the TRAINS_RTE_TRAIN.shp into postgis with the
following:
      shp2pgsql -d -I -s 26986 TRAINS_RTE_TRAIN.shp train_rte | psql
MY_GS_DB

then go into geoserver and try to make a new FeatureType out of this layer,
and get the following:
     GeoServer - Exception
     The following exception was thrown:
     java.lang.NullPointerException

with errors logged as such:
     http://transit.frumin.net/alewife/trains_rte.gsbug.txt

this is a first for a real GS crash for me. which means you guys rule!

-mike

PS I promise, I wont submit any more bugs to the mailing list before I file
the JIRA ones I owe you.

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org