Issue with TOC widget in 3.1

EricGardecki · ‎07-18-2014

I'm using flex viewer 3.1 (I had to revert to an older version to get each widget I am using to work) and am having an issue that seems to come from Robert's TOC widget (3.1.5), or at least something else affecting it.

If I have the widget set to preload, occasionally it will seemingly freeze up during load and be blank. The map layers then do not load either. This forces the user to refresh, which usually clears it up. I have since changed things to have the widget not preload, however (again, occasionally) when opening the widget it sometimes comes up blank and forces a refresh in order to turn on/off layers.

I can't figure out what is going on with it or why it is only occasionally.

I found this thread which led to a change that I applied but I'm not certain that it is the same issue or not. I haven't had enough time to see if that truly helps or not so I wanted to see if anyone knows if this is definitely the solution, and if not, what is?

thanks! !

EricGardecki · ‎08-06-2014

I've tried it with the TOC open and closed at load. When set as open, and it fails to load, it causes the whole app to fail to load and isn't usable. If set to be closed, everything else always works...they just may not be able to use the TOC when opening the widget as it may not load sometimes.

I've always used the default instance settings as i'm not sure of what to set to. I could try setting the max to 5 and see what happens. Which service would this be tied to? I have two map services loading, one basemap, one with features. Hmm..since the TOC is pulling from the latter (basemap isn't shown in TOC) maybe that would be the one?

RobertScheitlin__GISP · ‎08-06-2014

Eric,

I like Tracy's suggestion. Yes I would up the instances on your features map service

TracyArchibald · ‎09-04-2014

Sorry, been totally preoccupied with other projects!

I decided which services to up the numbers by logging into the Server manager and seeing which had the max instances running. Those ones I bumped up to 5. Then I checked again in an hour or so. If any of those were maxed out, I increased again. I repeated a couple of times until we didn't max out any more.