I'm trying to undestand what is happening with GeoServer/GeoWebCache integration.
Anyone has experienced GeoWebCache spending so much more time than WMS request to generate tile ?
In a simple test in my environment using embedded GWC in GeoServer, I also tested GWC in standalone mode, when I call a tile in GeoServer direct using WMS service the tile is returned in 18s, this same tile passing by GWC is spending more than 1min and return an error "400: ImageIO.read(InputStream) returned null. Unable to read image" because my WMS limit is 1min. In this specific case the tile has average of30.000 features. In other cases with less features GWC works well and return tiles without problems.
I thought that GWC just call GeoServer WMS service save the image returned and return the same to the client, so in this case if GeoServer spent 17s to return image to GWC, why the GWC can´t process this image in less than a minute ?
Something strange is that calling WMS Service directly the image is returned in 17s but using GWC the same request exceeds the WMS time limit that is 1min in this case and a error is throw in GeoServer log.
I'm using GeoServer 2.9.2 with GWC 1.9.1 and has tested GWC 1.9.2 standalone with the same results.
Anyone have any idea about it ?