Initialization of Site fails every morning
Hi,
I have a Site with several layers from different ArcGIS Server services. It is an ESRI problem that services from ArcGIS Server normally fails the first request after a long night sleep. And this problem seems to affect the REST Site as well.
When I make the first request to a Site in the morning, I get the following error:
Unable to load the Site from the Site.xml file located at C:\Program Files\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\InternWeb\Site.xml. The underlying exception message follows:A configuration error was encountered while deserializing the XML file C:\Program Files\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\InternWeb\Site.xml. Error message: Could not deserialize 'Map' element. Underlying cause: Could not deserialize 'MapServices' element. Underlying cause: Could not deserialize 'MapService' element. Underlying cause: Service 'wlan' of type 'MapServer' does not exist or is inaccessible.
When I look at the REST endpoint of the AGS service, I can see that it either fails the first time, or is really slow in responding. But after a few requests, everything works fine.
But the Site doesn't start working after the service is up and going. The only workaround I have found, is that I have to go into the Site.xml, add a blank line or something, save the file, and then make a new request to the Site.
0
-
Hi Joachim, We've experienced this issue with ArcGIS Server as well. It turns out that there's a setting which can be configured in an applicaiton pool of IIS which prevents this behavior. We've resolved this by removing the "Idle Time-out (minutes)" property of the application pools used by the ESRI REST API, and the Geocortex Essentials REST API.
I should also mention that Geocortex Essentials Manager for REST Elements (due to be released in Beta tomorrow) contains a "Reload" feature which allows you to reload a Site when the underlying map services may have changed. This should prevent you from having to make neglegable changes to the Site.xml in order to reload it. I hop this helps, Drew.
From: Joachim Eckbo Juell
Posted: Sunday, July 04, 2010 12:35 PM
Subject: Initialization of Site fails after long idle time
Hi,
I have a Site with several layers from different ArcGIS Server services. It is an ESRI problem that services from ArcGIS Server normally fails the first request after a long night sleep. And this problem seems to affect the REST Site as well.
When I make the first request to a Site in the morning, I get the following error:
Unable to load the Site from the Site.xml file located at C:\Program Files\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\InternWeb\Site.xml. The underlying exception message follows:A configuration error was encountered while deserializing the XML file C:\Program Files\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\InternWeb\Site.xml. Error message: Could not deserialize 'Map' element. Underlying cause: Could not deserialize 'MapServices' element. Underlying cause: Could not deserialize 'MapService' element. Underlying cause: Service 'wlan' of type 'MapServer' does not exist or is inaccessible.
When I look at the REST endpoint of the AGS service, I can see that it either fails the first time, or is really slow in responding. But after a few requests, everything works fine.
But the Site doesn't start working after the service is up and going. The only workaround I have found, is that I have to go into the Site.xml, add a blank line or something, save the file, and then make a new request to the Site.0 -
Thank you Drew,
I will try those changes in the AppPools. We also look forward to the 3.0 release :)0 -
Drew, if possible, could you elaborate on why turning off the idle timeout for the applicaiton pool of IIS prevents this behavior? 0 -
Hi Martin, The idle timeout property of an application pool causes the application pool to recycle after a period of inactivity. Sometimes, the first request to an ArcGIS Server map service following the recycle of an application pool (due to the idle timout, or a forced recycle) causes a delay. I can't be certain why the initial request to a map service following this event triggers this delay - perhaps Esri is the best avenue for that question.
I'll see if we can find out a bit more about this... in the meantime, you may wish to contact some of the folks at Esri to see if they can shed some light on the subject. Drew.0 -
Thanks Drew. Yeah I realized that this is a question for ESRI, I just wanted to check if you had been down that route before. So far I've been unable to find a consistent way of reproducing the behaviour, so ESRI probably won't be able to help. Even if you do work around this issue by turning off the idle timeout in IIS, the application pool will have to recycle from time to time. In those cases the error could return, I would think. I guess a scheduled recycling of IIS followed by an automatic REST request would be needed? Ottar (borrowing Martin's account) 0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
5 commentaires