Hello Brett,
thank you for forwarding my previous response to the mailing list :-)
The error shown in the console might or might not be the source of your
problem. According to the current OpenLayers source code, error #25 originates
in the method 'View.fit'
(https://github.com/openlayers/openlayers/blob/master/src/ol/View.js#L981)
which is called with an empty 'geometryOrExtent' parameter. As this happens
before your first interaction with the webseite I assume that there is a
problem with setting the intial map extent.
To track down the real problem you should have a look at the configuration of
your OpenLayers web application. There must be some kind of difference between
'old' and 'new' layers. If the app is configured by reading the content of the
service's GetCapabilities document, maybe the error originally comes from the
server. The only other possibility I see at the moment would be to debug the
client javascript to see exactly what is happening when you activate the 'bad'
layer.
Regards
Daniel
From: Carlock, Brett [mailto:bcarl...@agrinetix.com]
Sent: Monday, August 6, 2018 5:57 PM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Newly added layers not rendering with GeoServer
2.13.2
Hello again!
I used the F12 Developer Tools in Edge to investigate the difference between a
Good request against a layer I know works versus a Bad request against one of
the newly added layers, and have attached a 7z archive of the two HAR (JSON)
logs to this reply. This website can be used to visualize the HAR logs nicely:
http://www.softwareishard.com/har/viewer/
>From my limited understanding, the Good Request proceeds as I assume it
>normally would, and after I click the toggle button to load the layer in our
>UI, it makes a series of GET WMS requests which return PNG tiles. This is how
>I believe things should go, and the layer draws just fine.
When I read the Bad request, it proceeds pretty much exactly the same as the
Good request up until the point where I toggle the layer on with the checkbox
in our UI. The log stops there. Absolutely nothing happens, which I suppose
makes sense given that I observed no information about a failure in the logs
for geoserver/Tanuki wrapper, and the files seem to not be malformed.
The only other thing of note I observed in the F12 Developer Tools is this log
entry in the Console:
0: AssertionError: Assertion failed. See
https://openlayers.org/en/v4.6.4/doc/errors/#25 for details.
The error description reads as follows: (25: Cannot fit empty extent provided
as geometry.)
This error shows up before I interact with our website UI in any way, and does
not seem to impact whether or not a layer draws as it is present before I turn
on known-good working layers.
Does this definitively mean that the issue lies with our OpenLayers UI, or am I
not fully understanding how these systems interact yet?
Thank you all so much for your time and assistance, and especially thanks to
Daniel for pointing me in the direction to take a closer look at what is going
on.
Brett
Instructions/Reply from Daniel quoted below:
"Hi Brett,
if the tiles do not show up on your website, the first thing to try would be
checking the requested URLs and the response from the server. Press the "F12"
key in your browser or open "Developer Tools" from the menu and switch to the
"Network" tab. Reload the page or zoom/pan the map and the tile requests should
be listed. Look out for differences in the URLs of tiles of working and broken
layers and also check the HTTP status code for "200 OK" or "304 Not Modified"
with would be fine or "500 Server Error" in case of problems on the server. A
look in the details of a single request might be interesting too, are valid
pictures returned (Content-Type, Content-Length)? Maybe the server is
responding properly but the images are blank/transparent.
You could also install a tool like "Fiddler" and redirect the traffic of QGIS
to the Fiddler proxy to be able to compare the successful requests of QGIS with
the unsuccessful requests of the website client.
Let us know what you found out.
Regards
Daniel"
From: Carlock, Brett
Sent: Friday, August 3, 2018 4:09 PM
To: geoserver-users@lists.sourceforge.net
Subject: Newly added layers not rendering with GeoServer 2.13.2
Hi! Firstly, thanks for your excellent software. GeoServer is an amazing tool
and I have rather enjoyed my time learning about it this past year.
Background:
Windows x64 Host (Server 2012)
Oracle JRE8v181 x86
Pure Java JAI/JIO
GeoServer v2.13.2 installed as a Service with the Tanuki Wrapper
GeoServer data-dir that has been migrated from 2.5.x up to 2.13.2
Semi-Manual rename of files/folders and edits of coverage/layer/store xml files
to make everything XML-Safe accomplished by me when migrating from 2.8.x to
versions beyond (2.12.3) [a whole other issue :C]
Things worked fine until migration from 2.12.3 to 2.13.0.
Issue summary:
Layers that I add with new Stores (for example: Rx.tiff or Rx.shp with
associated SLD) will be rendered perfectly fine in the Preview Layers section
in GeoServer, as well as being able to be seeded/cached using the embedded GWC,
and the cached tiles previewed perfectly fine through the GWC Tile Layers
Preview function.
QGIS v2.18.22 and v3.2.1 load/display/query the above layers perfectly fine.
Gdalinfo does not report anything that appears to be amiss to me.
These same layers WILL NOT draw/display through our website wrapper (based upon
OpenLayers), yet layers that existed prior will render just fine.
Neither the wrapper log nor the data-dir log seem to throw any
exceptions/info/warn when those layers are "turned on" in our web wrapper.
I've looked through the mailinglist, Bing/Google, SE, SO and have not come
across this issue before.
I've almost convinced myself that nuking our data-dir and rebuilding manually
would be worthwhile since I'm sure I introduced some funkiness when I did my
XML-Safe sprint to get beyond 2.8.x, but there are around 1000 layers/stores
and about 230 workspaces, so I'm hoping I can (with some
help/guidance/knowledge) fix up what we have running.
Thank you sincerely for your time and any help I may receive,
Brett
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
