All,
I have recently upgraded from GS 1.4 to 1.6 RC2 (on linux with JDK
1.6.0_03). One of my applications does some calculations on the client side
and then makes a wfs request with a filter to get some geometries. The
request may at times request up to 2500 features. This has always worked
smoothly with GS 1.4, but now with 1.6 it crashes at 700 or so features. By
crash I mean I get an error (in geosererver logs) that looks like this:
2008-01-04 10:49:06,816 ERROR [org.geotools.rendering] -
java.lang.StackOverflowError
at
org.geotools.filter.FilterCapabilities.supports(FilterCapabilities.java:431)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visitLogicO
perator(PostPreProcessFilterSplittingVisitor.java:617)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visit(PostP
reProcessFilterSplittingVisitor.java:600)
at org.geotools.filter.AndImpl.accept(AndImpl.java:60)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visitLogicO
perator(PostPreProcessFilterSplittingVisitor.java:672)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visit(PostP
reProcessFilterSplittingVisitor.java:600)
at org.geotools.filter.AndImpl.accept(AndImpl.java:60)
...with the final three lines repeating for the number of features
requested. The same thing happens when I use a similar filter to make a wms
request. Again, these both worked well with 1.4.
The filter in both cases is something like this:
<Filter><Or>
<PropertyIsEqualTo>
<PropertyName>areasymbol</PropertyName>
<Literal>AL003</Literal>
</PropertyIsEqualTo>
<PropertyIsEqualTo>
<PropertyName>areasymbol</PropertyName>
<Literal>AL009</Literal>
</PropertyIsEqualTo>
..........
</Or></Filter>
And I must say that we have generally had memory leak problems since going
to 1.6. I know have the min and max heap size set to -Xms64 -Xmx1024, which
is higher than I had previously for 1.4
Any thoughts?
Thanks again,
Steve
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
Stephen Crawford ha scritto:
All,
I have recently upgraded from GS 1.4 to 1.6 RC2 (on linux with JDK
1.6.0_03). One of my applications does some calculations on the client side
and then makes a wfs request with a filter to get some geometries. The
request may at times request up to 2500 features. This has always worked
smoothly with GS 1.4, but now with 1.6 it crashes at 700 or so features. By
crash I mean I get an error (in geosererver logs) that looks like this:
2008-01-04 10:49:06,816 ERROR [org.geotools.rendering] -
java.lang.StackOverflowError
at
org.geotools.filter.FilterCapabilities.supports(FilterCapabilities.java:431)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visitLogicO
perator(PostPreProcessFilterSplittingVisitor.java:617)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visit(PostP
reProcessFilterSplittingVisitor.java:600)
at org.geotools.filter.AndImpl.accept(AndImpl.java:60)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visitLogicO
perator(PostPreProcessFilterSplittingVisitor.java:672)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visit(PostP
reProcessFilterSplittingVisitor.java:600)
at org.geotools.filter.AndImpl.accept(AndImpl.java:60)
...with the final three lines repeating for the number of features
requested. The same thing happens when I use a similar filter to make a wms
request. Again, these both worked well with 1.4.
The filter in both cases is something like this:
<Filter><Or>
<PropertyIsEqualTo>
<PropertyName>areasymbol</PropertyName>
<Literal>AL003</Literal>
</PropertyIsEqualTo>
<PropertyIsEqualTo>
<PropertyName>areasymbol</PropertyName>
<Literal>AL009</Literal>
</PropertyIsEqualTo>
..........
</Or></Filter>
And I must say that we have generally had memory leak problems since going
to 1.6. I know have the min and max heap size set to -Xms64 -Xmx1024, which
is higher than I had previously for 1.4
We were not aware of either problem, so I don't have a workaround for you. This seems serious, but I need more information in order to reproduce it.
Which datastore are you using?
Is there any chance you can give us a sample of your data and a request
that makes GeoServer break?
Cheers
Andrea
I am having the same problem. The sld I created validates(has 1900 features).
When a request is made we get a geoserver error:
[org.geotools.rendering] -java.lang.StackOverflowError
I can send my sld and shapefile if it helps resolve the problem.
Stephen Crawford wrote:
All,
I have recently upgraded from GS 1.4 to 1.6 RC2 (on linux with JDK
1.6.0_03). One of my applications does some calculations on the client
side
and then makes a wfs request with a filter to get some geometries. The
request may at times request up to 2500 features. This has always worked
smoothly with GS 1.4, but now with 1.6 it crashes at 700 or so features.
By
crash I mean I get an error (in geosererver logs) that looks like this:
2008-01-04 10:49:06,816 ERROR [org.geotools.rendering] -
java.lang.StackOverflowError
at
org.geotools.filter.FilterCapabilities.supports(FilterCapabilities.java:431)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visitLogicO
perator(PostPreProcessFilterSplittingVisitor.java:617)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visit(PostP
reProcessFilterSplittingVisitor.java:600)
at org.geotools.filter.AndImpl.accept(AndImpl.java:60)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visitLogicO
perator(PostPreProcessFilterSplittingVisitor.java:672)
at
org.geotools.filter.visitor.PostPreProcessFilterSplittingVisitor.visit(PostP
reProcessFilterSplittingVisitor.java:600)
at org.geotools.filter.AndImpl.accept(AndImpl.java:60)
...with the final three lines repeating for the number of features
requested. The same thing happens when I use a similar filter to make a
wms
request. Again, these both worked well with 1.4.
The filter in both cases is something like this:
<Filter><Or>
<PropertyIsEqualTo>
<PropertyName>areasymbol</PropertyName>
<Literal>AL003</Literal>
</PropertyIsEqualTo>
<PropertyIsEqualTo>
<PropertyName>areasymbol</PropertyName>
<Literal>AL009</Literal>
</PropertyIsEqualTo>
..........
</Or></Filter>
And I must say that we have generally had memory leak problems since going
to 1.6. I know have the min and max heap size set to -Xms64 -Xmx1024,
which
is higher than I had previously for 1.4
Any thoughts?
Thanks again,
Steve
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
View this message in context: http://www.nabble.com/1.6-RC2-problems-tp14620482p14846129.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
jmbeaudoin ha scritto:
I am having the same problem. The sld I created validates(has 1900 features).
When a request is made we get a geoserver error:
[org.geotools.rendering] -java.lang.StackOverflowError
I can send my sld and shapefile if it helps resolve the problem.
Hum, Stephen problem should have been solved. Yours, I don't know...
are you using a database or a shapefile? If a database, the issue
should be fixed in RC3, if a shapefile, it's new to me. In the latter case, please open a jira issue and attach the sld and the data.
Cheers
Andrea