Thanks Ian and Andrea, Sorry, I didn't mean to come across as pushy Andrea. I didn't think you were ignoring me; to be honest I just decided to pick it up again briefly this morning as I've been doing other work all week.
The trouble is that we have so many factors that could be at play, the data we have loaded is much bigger than a sample and if the error is relating to the quantity of records to sort then a sample is unlikely to replicate the error. My research into the issue so far seems to indicate that the data may not be the issue but perhaps it is something to do with the Oracle driver or the way GWC is monitoring the seed request. Whilst I note your comment the stack trace below mentions the disk quota which is something we did look at using but decided against. There are a few odd error messages I've never been able to resolve on our system including No JTDS jar on classpath and an incorrect JDBC password which I can't track down. I wondered if the password was linked to the disk quota but I have been ignoring it as we don't use the disk quota and the error is not linked to anything noticeable. It tends to appear at start up mostly. The layers being used are relatively large and in an Oracle database. The styles being applied are also relatively complex and the Oracle data is actually being provided by views loaded into GeoServer as sql_views. Add to this the complication of using a layer group and sorting Z index across the layers and it is quite an ask for the renderer; hence why I'm keen to cache. Should I try it without the z grouping across layers and see if it runs? Paul From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: 19 August 2016 10:32 To: Paul Wittle Cc: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] Looking for advice on issues with sorted rendering when seeding a layergroup Hi Paul, I'm not ignoring you, I did not follow up because I don't have anything else to add, without a way to reproduce I won't be able to help. The stack traces you've shared indeed do not point to a particular location, sorry. I checked, it does not seem like GWC is logging the internal request made by the tile seeder (which would have been a better way to locate the problematic area), but who knows, maybe increasing the geoserver logging level to "devel" mode might provide some hints. Cheers Andrea On Fri, Aug 19, 2016 at 11:14 AM, Paul Wittle <p.wit...@dorsetcc.gov.uk<mailto:p.wit...@dorsetcc.gov.uk>> wrote: Hi Andrea, As I said offline I'm going to be struggling with the data sample as this is happening when using OS MasterMap data. I've run it again with a load of debugging options on in order to try and see if I could log which bbox was being processed when it fails. As yet I have still not managed to find an issue it terms of the actual tiles as they seem to generate fine but then kill the thread. I did find this stack trace: t(LayerCacheInfoBuilder.java:274) at org.geowebcache.util.FileUtils.traverseDepth(FileUtils.java:100) at org.geowebcache.util.FileUtils.traverseDepth(FileUtils.java:106) at org.geowebcache.diskquota.LayerCacheInfoBuilder$ZoomLevelVisitor.call(LayerCacheInfoBuilder.java:235) at org.geowebcache.diskquota.LayerCacheInfoBuilder$ZoomLevelVisitor.call(LayerCacheInfoBuilder.java:187) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException at org.geowebcache.diskquota.LayerCacheInfoBuilder$ZoomLevelVisitor.accept(LayerCacheInfoBuilder.java:274) at org.geowebcache.util.FileUtils.traverseDepth(FileUtils.java:100) at org.geowebcache.util.FileUtils.traverseDepth(FileUtils.java:106) at org.geowebcache.diskquota.LayerCacheInfoBuilder$ZoomLevelVisitor.call(LayerCacheInfoBuilder.java:235) at org.geowebcache.diskquota.LayerCacheInfoBuilder$ZoomLevelVisitor.call(LayerCacheInfoBuilder.java:187) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) log4j:WARN File option not set for appender [geoserverlogfile]. log4j:WARN Are you using FileAppender instead of ConsoleAppender? Does that give any better clues? It was in the tomcat8-stderr log and I think it might have been because I seleted the log to stdOut option. Thanks, Paul From: andrea.a...@gmail.com<mailto:andrea.a...@gmail.com> [mailto:andrea.a...@gmail.com<mailto:andrea.a...@gmail.com>] On Behalf Of Andrea Aime Sent: 16 August 2016 09:32 To: Paul Wittle Cc: geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net> Subject: Re: [Geoserver-users] Looking for advice on issues with sorted rendering when seeding a layergroup Hi Paul, thanks for the stack trace. I had a look at the code but nothing stands out. In order to debug this one I'll need a bug report, with a small enough set of sample data, styles, and a request that makes it happen Cheers Andrea On Tue, Aug 16, 2016 at 10:10 AM, Paul Wittle <p.wit...@dorsetcc.gov.uk<mailto:p.wit...@dorsetcc.gov.uk>> wrote: Hi Andrea, Stack trace follows and the version is 2.8.4. Thanks, Paul --- Stack trace 2016-08-08 11:17:54,600 ERROR [geotools.rendering] - The sorted rendering moved from a set of sort attributes, to one that's equal or greater, this is unexpected, bailing out to avoid an infinite loop java.lang.IllegalStateException: The sorted rendering moved from a set of sort attributes, to one that's equal or greater, this is unexpected, bailing out to avoid an infinite loop at org.geotools.renderer.lite.ZGroupLayer.drawFeatures(ZGroupLayer.java:105) at org.geotools.renderer.lite.StreamingRenderer.paint(StreamingRenderer.java:813) at org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:538) at org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:259) at org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:132) at org.geoserver.wms.GetMap.executeInternal(GetMap.java:505) … at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2407) at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2396) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Unknown Source) 2016-08-08 11:17:54,600 ERROR [geoserver.ows] - org.geoserver.platform.ServiceException: Rendering process failed at org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:568) … Caused by: java.lang.IllegalStateException: The sorted rendering moved from a set of sort attributes, to one that's equal or greater, this is unexpected, bailing out to avoid an infinite loop at org.geotools.renderer.lite.ZGroupLayer.drawFeatures(ZGroupLayer.java:105) at org.geotools.renderer.lite.StreamingRenderer.paint(StreamingRenderer.java:813) at org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:538) ... 146 more 2016-08-08 11:17:56,475 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks "This e-mail is intended for the named addressee(s) only and may contain information about individuals or other sensitive information and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this email in error, kindly disregard the content of the message and notify the sender immediately. Please be aware that all email may be subject to recording and/or monitoring in accordance with relevant legislation."
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
