Problems with REST Manager
Has anyone been having with REST Manager being quite flaky? I find that every 2nd or 3rd time using it, it will hang when I'm trying to apply changes, or save a site. Usually I have to close the browser and start it up again to get it to work. This happens with IE/Chrome/FF, and is quite annoying. I'm running Essentials 3.10, although this behavior has been happening with all the earlier versions I've used.
Chris
-
To answer your question, yes, I have the 3.10 Manager hang on me all the time and previous version also. It definitely affects productivity. I don't have an explanation for it. Sometimes I wonder if I click too fast. But even when I wait and go slower, it still happens. Like you, it occurs when submitting changes on a page and when saving. The behavior is not very reassuring.
0 -
same here, not sure why
0 -
Hi Guys,
Does the hang always happen when applying changes on the same page, or does it happen on all pages? If it's isolated to just one page, that narrows down our search.
Chris, are you working with layer themes? Do you duplicate layer names in any of your services? If so, check the file size of the Site.XML file. If it's over 500KB then you may have triggered a problem with REST Manager where it adds the theme settings too many times to each layer. You'll see lots of <ThemeSetting> tags within the Site.xml.
Regards,
-Malcolm
0 -
Hi Malcolm. It happens on random pages, including both the site, and the viewer - nothing consistent that I can figure out.
I only have layer themes set up on one site, so that's not the problem. Our main site's site.xml is 138K, and it doesn't have layer themes.
I don't have duplicate layer names within a service, but do have some duplicates across map services. Could this be a problem?
Chris
0 -
Hi Malcolm,
I had created another post in the forum with the same issue.
https://support.geocortex.com/SupportForums/Thread.aspx?thread=47439&mid=2&pageid=0&ItemID=2
I am experiencing almost exactly what Chris is. I am not working with layer themes, our main site .xml is 198kb and like Chris I don't have duplicate layer names within a service, but do have some duplicates across map services.
Something I find interesting is we are running two servers (development and production). Our development server hangs rarely while our production server hangs every two or three save attempts. The geocortex sites are identical (as the site folder was copied from development to production in window explorer).
The only differences between the development and production server is more applications running on the production server (Dot Net Nuke, sql etc...) so maybe another application could be conflicting? and it is running windows server 2003, while the development box is running window server 2008.
Gordy
0 -
Still having the same issues, It is getting very frustrating.
Any Ideas?
Thanks, Gordy?
0 -
I'm also having problems with Essentials Manager and my Site.xml is 2,748KB and my problem occurs when I edit the Layer Themes. I contacted GeoCortex back in April about the problem and then it seem the problem was related to many Layer Themes / map service layers. I made a copy of my Site.xml and on 10/18/2012 it was 284KB and today it is 2,748KB.
So, what do I do for the Layer Theme problem.
Thanks
Jimmy Brink
0 -
After looking at my Site.xml there is something going on. My Site.xml is 63,333 lines long and there is a lot of the duplicates in it (see below). I made a copy of the Site.xml and then found 5 layers in the Site.xml that had <ThemeSetting ID = "1" /> duplicated lots of times. I deleted 60,098 lines in the Site.xml that had the duplicates in them. My Site.xml went from 2748KB to 224KB and the lines went from 63,333 to 3235. I then saved the Site.xml and restarted Essentials Manager. My Site works now in Manager and I can modify the Layer Themes.
So, GeoCortex how does the Site.xml get the duplicates in it?
Jimmy Brink
<ThemeSettings>
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />
<ThemeSetting ID="1" />0 -
Hi Jimmy,
One of your group layers contains a layer that has a duplicate name.
This duplicated name causes REST Manager to incorrectly add the layer theme settings when you manage themes (it will double or triple the entries, or worse). Right now the only resolution is to either rename your layers or manually remove the duplicates.
We have filed this issue in our system and it will be resolved in a future version of Essentials.
0 -
Malcolm,
That is good to know about layers having the same name. Unfortunately that does not help us as we do not have layers with multiple 'same' names or themes.
As stated before I fine in strange as we are running two servers (development and production). Our development server hangs rarely while our production server hangs every two or three save attempts. The geocortex sites are identical (as the site folder was copied from development to production in window explorer).
Any Ideas for this issue?
Thanks Gordy
0 -
Hi Gordy,
Duplicate layer names in a group layer cause the problem where the Site.XML grows out of control and slows down to the point of crashing. I understand that your Site.XML is a constant size so this problem / solution will not affect you.
Since you have a working development server and a broken production server, that appear to be identical, we should focus on the differences between those two servers to determine what you are experiencing.
We generally assume that other web applications on a server do not affect the way we operate; when you install Essentials it deploys its own users and application pools, which are the sandboxes in which the applications run. However, if the total capacity of the server is insufficient to allow Essentials to run, then we may be hitting memory, CPU, or disk limits when Essentials is operating. This sort of problem will usually be apparent in the Windows Event Logs, particularly the System and Application logs. If there are any ASP.NET messages in your event logs, please review them to see if ASP.NET is complaining about a lack of memory, or a thread being aborted, or a System.OutOfMemoryException.
It is important for us to determine if your hang is an actual hang, where the computer is busy working and needs more time to complete, or a perceived hang, where it has already errored out and is either waiting for feedback from you or just stuck in an error state.
Note that the activity spinner is an animated GIF and will continue to spin when nothing is actually happening. Use your web browser's activity indicator (usually a spinner on the tab title, or a progress bar in the lower-right) to determine if the browser is still waiting for a response from the server.
It is also useful for us to have a Fiddler capture of a user session, and screen shots of what the administrator sees when the problem arises. Is there a yellow exclamation mark in the browser status bar? A popup? An alert telling you that a popup was blocked?
Regards,
-Malcolm
0 -
Any ideas yet?
0 -
Still not solution
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
13 Kommentare