Dear all,
I'm not really sure what is the deal here. We have a 2.0.2 install with
quite a lot of data, all the feature layers are in postgis. After adding
a few more layers, all our WFS requests fail with this exception:
java.lang.NullPointerException
at
org.geotools.jdbc.JDBCDataStore.createConnection(JDBCDataStore.java:1420)
at
org.geotools.jdbc.JDBCDataStore.getConnection(JDBCDataStore.java:1377)
at
org.geotools.jdbc.JDBCFeatureSource.getReaderInternal(JDBCFeatureSource.java:545)
at
org.geotools.jdbc.JDBCFeatureStore.getReaderInternal(JDBCFeatureStore.java:209)
at
org.geotools.data.store.ContentFeatureSource.getReader(ContentFeatureSource.java:481)
at
org.geotools.data.store.ContentFeatureCollection.features(ContentFeatureCollection.java:217)
at
org.geotools.data.crs.ReprojectFeatureResults.openIterator(ReprojectFeatureResults.java:108)
at
org.geotools.feature.collection.AbstractFeatureCollection.iterator(AbstractFeatureCollection.java:334)
at org.geotools.xml.Encoder.encode(Encoder.java:996)
at org.geotools.xml.Encoder.encode(Encoder.java:561)
at
org.geoserver.wfs.xml.GML3OutputFormat.write(GML3OutputFormat.java:190)
at
org.geoserver.wfs.WFSGetFeatureOutputFormat.write(WFSGetFeatureOutputFormat.java:137)
at org.geoserver.ows.Dispatcher.response(Dispatcher.java:726)
at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:234)
at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
It seems related to postgis refusing connection, which is probably
related to the connection parameters in the store, which we keep quite
low (usually 5 max, 2 min). But if so, I guess I never quite understood
how to use that properly. Our postgis has a 200 connection limit, quite
high, and postgres reports only 82 in use when geoserver is running.
Even if this is the reason, does it mean I am limited in the number of
layers unless I put 0 as min connections? Is the latter a possible
solution? Or is it something else entirely?
Thanks for any insight, we're running a large system here and geoserver
downtime is a big deal for us.
ferdinando
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
