Hello there,
I will be very happy if you can answer these questions and problems.
We have been using Geoserver 2.1.3 and then 2.2 but we faced with some
problems while using it in our projects. They are:
1- What if table is empty? There will be no SRID defined (in mssql 2008 r2)
so that might cause problems? Is it safe to add empty tables to geoserver?
1.2- What if there are some rows in the table which have null geometry? That
causes a problem?
2- What if there are geometries which are not valid? Is it safe or not safe?
3- What if there are some geometry collections in a table? What is the
impact? As far as I know shape files cannot accept "geometry collection" but
is it harmful for geoserver as well?
4- We have spatial indexes in all tables in MSSQL 2008 r2 but we are getting
data from views of these tables, still spatial indexes will work or not?
5- Let's say 100 row of table has SRID 4326 but one row has 900913 then what
is the impact on geoserver if we add this table.
6- We have some tables that geoserver cannot use its spatial index because
of a bug in database server. Mssql 2008 r2 bug happens when there are many
cores in the machine (128 in our case), so query optimizer cannot understand
spatial index usage will be helpful then tries to use normal index. Is there
a way to force geoserver to use particular indexes in mssql? For example :
with(index(x index)) command etc.
7- What can be the cause of "PermGen space" error? There is enough memory
for permgen but periodically we are getting this error. That can be because
of some problematic data? That happens mostly in Geoserver 2.2 and I
couldn't find bug reports related with it.
I am asking these questions because either 2.1.3 or 2.2 every few hours
geoserver becomes unreachable. Thank you already,
Best Regards.
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/Geoserver-2-1-3-2-2-some-problems-and-questions-tp5020078.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
