On Thu, Nov 4, 2010 at 4:05 AM, Volker Grabsch <[email protected]> wrote:
> Justin Deoliveira <[email protected]> schrieb:
> > GeoServer writing should be constrained to tmp space and the geoserver
> data
> > directory as far as i know. I have never seen this before:
> >
> > /home/USER/.java/.userPrefs/org/geotools/
> >
> > Not sure where it comes from. But as far as I know if you want a clean
> > restart simply removing any of the temp files should do it. And actually
> > just the geotools tmp files for the epsg database. Other temp files
> created
> > by geoserver will not be used on a successive run. Unless there is a
> serious
> > bug i am unaware of.
>
> Is that also true for the app-schema plugin?
>
Hmmm.. not sure about that. The app-schema maintainers will have to answer
that.
>
>
> > On Thu, Sep 9, 2010 at 5:10 PM, Volker Grabsch <[email protected]> wrote:
> > > To be more concrete, I regularly receive the following exception
> > > on each WFS request after a fresh GeoServer restart:
> > >
> > > org.geoserver.platform.ServiceException:
> > > java.lang.RuntimeException:
> > > java.io.IOException:
> > > Error occurred trying to reproject data
> > > ... [1]
> > >
> > > This error message is misleading because there are absolutely no
> > > projection issues or other issues with our geo data. In fact, the
> > > exception always disappeared after 1-5 restarts of GeoServer.
> > >
> > As for the issue at hand i am not sure it is the case of stale state
> being
> > kept around. When you say there are "no projection issues" with the
> dataset
> > what do you mean? What projection is the data in natively? Does GeoServer
> > properly detect this when it configures the layter? And what projection
> are
> > publishing it as?
>
> With "no projection issues" I meant that GeoServer outputs the correct
> data in the correct projection - if it outputs anything.
>
> In other words, everytime we start GeoServer, exactly one of two things
> happens:
>
> 1) GeoServer runs flawlessly, without any projection issues or
> any other issues.
>
> 2) GeoServer fails on _every_ GetFeature request, throwing the
> above mentioned exception message.
>
> The only way to switch between these two modes is restarting the
> GeoServer. So if GeoServer starts in mode 2), we'll have to restart
> it and restart it (up to 5 times) until it "switches back" to mode 1).
>
> Hmmm... very strange. Although I ran into a similar issue with one of our
servers recently where the WFS returned an exception for every request and
the only cure was to restart. Which was troubling. And the server was not
emitting any sort of stack trace which is even more troubling.
Unfortunately not much i can say. Do you have any full stack traces of the
errors that are occurring?
>
> > Also one thing to keep in mind is that with wfs 1.1 the coordinate order
> for
> > most geographic coordinate systems is swapped, so its lat,lon and not
> > lon,lat which most data is always in. So if you make the same wfs call
> with
> > 1.0 vs 1.1 the 1.1 request usually results in a reprojection to swap the
> > coordinates.
>
> We are consistently using WFS-1.1, and had no issues with swapped
> coordinates yet, at least in mode 1).
>
>
> Greets,
> Volker
>
> --
> Volker Grabsch
> ---<<(())>>---
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
