NIM043400 for ArcGIS Server (.NET)

Bug-ID-Nummer	NIM043400
Eingereicht	March 18, 2009
Zuletzt geändert	April 2, 2025
Gilt für	ArcGIS Server (.NET)
Gefunden in Version	9.3
Status	Known Limit

Zusätzliche Informationen

No Public Explanation

Workaround

There are a couple of ways you can help you get the behaviour you are looking for:Before reading the workaround - Please read the support article " HowTo: Caching and Route Events"http://support.esri.com/index.cfm?fa=knowledgebase.techArticles.articleShow&d=25846Depending on the requirements or the audience of your map service you may chose one of these options over the other. Maybe it's ok events to only be updated every couple of hours... if that's the case setting approach #2 below i.e the recycling property would because then you can benefit from the dynseg cache.To publish a mapservice that contains Events layer, an author can choose from the following two options:• #1: Turn off the DynSeg cache for the ArcGISSoc user. This will mean that the event table will be re-read each time the events are displayed (i.e during pan, zoom etc). Downside to this solution is that, depending on the size of the table, this can be slow to draw - because we are rereading from teh table and re-calculating the shapes of the events (Note with the Dynseg cache on we cache events, so although the initial draw may be slow, subsequent draws will be faster (Read the KB article for more info To do this - change the registry setting for the user whom the SOC is "running as" so that event data will not be cached by the mapserver. This is more appropriate to the scenario where event table gets updated very frequently and down-time is not an option. The disadvantage of that (as you mentioned) will be the performance hit, it may slow down depends on the size of the event table. Please see the KB article (http://kbplus/kbdoc.asp?dbid=25846) for more information on event caching and it has a script that allows user to disable the caching. It is very important that the user log on to that machine as the SOC user and run the script to disable event caching.OR, • #2: leave the setting to what it is (event data is cached by mapservice during the startup of the service) and (a) restart the service once editing is done or (b) change the "recycle" property so that the service will be restarted automatically every few hours...