Hi,
as you may know GeoServer has a small set of online tests
checking wfs and wms cascading that need a remote WMS/WFS
server to be up and running with the GeoServer demo data sets.
So far http://demo.opengeo.org/geoserver has been playing that role,
however lately it has been unreachable/very slow and
thoses tests actually fail or get skipped.
Not very many people notice that because one has to explictly enable
online tests (not sure if any of the build do), I actually noticed
only yesterday while working on GetFeatureInfo property selection
while I was adding tests for property selection on top of cascaded
GetFeatureInfo (which is an online test).
In the end to build the test I had to start a local geoserver and run
the tests against it.
So I was wondering what to do about it. I likely could stand-up a vanilla
GeoServer somewhere on demo.geo-solutions.it that takes the
place of demo.opengeo.org/geoserver and then update the tests?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
Just kicked the server and it seems to be normally responsive again.
We have a watchdog running on that server but it seemed to only be checking the wms capabilities request, which i guess was still responsive… looks like adding some additional checks is in order.
What tests in particular use the server? I can add checks explicitly for those layers to ensure they remain responsive.
On Thu, Mar 1, 2012 at 12:40 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi,
as you may know GeoServer has a small set of online tests
checking wfs and wms cascading that need a remote WMS/WFS
server to be up and running with the GeoServer demo data sets.
So far http://demo.opengeo.org/geoserver has been playing that role,
however lately it has been unreachable/very slow and
thoses tests actually fail or get skipped.
Not very many people notice that because one has to explictly enable
online tests (not sure if any of the build do), I actually noticed
only yesterday while working on GetFeatureInfo property selection
while I was adding tests for property selection on top of cascaded
GetFeatureInfo (which is an online test).
In the end to build the test I had to start a local geoserver and run
the tests against it.
So I was wondering what to do about it. I likely could stand-up a vanilla
GeoServer somewhere on demo.geo-solutions.it that takes the
place of demo.opengeo.org/geoserver and then update the tests?
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.