New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hazardous map error during viewer loading #164

Closed
GROUSSEL opened this Issue Jul 15, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@GROUSSEL

GROUSSEL commented Jul 15, 2013

Hi,

Sometimes, we encounter the following error during loading of the viewer for flex (last case encountered with a viewer 3.4)

mapmanager


La couche Points de Vigilance n’a pas été chargée : Code d’erreur : Server.Error.Request
Informations sur l’erreur : Erreur de requête HTTP
Détails de l’erreur : Erreur : [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032: Erreur de flux. URL: http://XXX.net/ArcGIS/rest/services/XXX/FeatureServer/0?f=json"]. URL: http://XXX.net/ArcGIS/rest/services/XXX/FeatureServer/0?f=json


It appears both regarding basemaps but also on operational layers (Mapserver, FeatureServer…). The trouble is NOT permanent (!). Moreover a simple refresh (F5) is enough to cancel this error.

In viewers for flex <=2.5, we made some (dirty) modifications in the \src\com\esri\viewer\managers\MapManager.mxml file to do N attempts delayed of M milleseconds (N and M defined in the config.xml file) in case of failed load. Unfortunately, this correction is not effective with a viewer 3.x

Do you have any idea on what to do to correct this ?

Thank you in anticipation !

Guillaume

@bsvensson

This comment has been minimized.

Show comment
Hide comment
@bsvensson

bsvensson Jul 15, 2013

Member

Hi Guillaume,
Since this only happens sometimes, it sounds to me like this is more of a server or web server issue. You shouldn't have to make multiple attempts to make it work.

I would recommend contacting Esri Support - http://support.esri.com for help with debugging the server issue. The Flex API and Viewer forum is another great place for getting practical help from users which might have had similar issues. If the server problems can't be fixed, either Support or Forum might be able to help migrate your 2.x workarounds.

Member

bsvensson commented Jul 15, 2013

Hi Guillaume,
Since this only happens sometimes, it sounds to me like this is more of a server or web server issue. You shouldn't have to make multiple attempts to make it work.

I would recommend contacting Esri Support - http://support.esri.com for help with debugging the server issue. The Flex API and Viewer forum is another great place for getting practical help from users which might have had similar issues. If the server problems can't be fixed, either Support or Forum might be able to help migrate your 2.x workarounds.

@bsvensson bsvensson closed this Jul 15, 2013

@GROUSSEL

This comment has been minimized.

Show comment
Hide comment
@GROUSSEL

GROUSSEL Jul 16, 2013

Hi Bjorn,

Thank you for your reply.

Maybe you are right, but we have this problem on a lot of different platforms, with different server configurations and viewers for flex… When it occurs, it is always when the viewer contains many services (>5). And without any error on the server side.

We found a similar post on the “ArcGIS Viewer for Flex” forum but without a fully satisfying response:
http://forums.arcgis.com/threads/81349-FlexViewer-2.5-MapManager-Error-400?highlight=mapmanager

The workaround with delayed attempts we have implemented on the Viewer <=2.5 solved the problem: the error never reappeared. That’s why we tried to carry out an equivalent modification with viewers >2.5. But having difficulties to do so, and not being the only one to encounter this bug, we thought best to turn to you.

GROUSSEL commented Jul 16, 2013

Hi Bjorn,

Thank you for your reply.

Maybe you are right, but we have this problem on a lot of different platforms, with different server configurations and viewers for flex… When it occurs, it is always when the viewer contains many services (>5). And without any error on the server side.

We found a similar post on the “ArcGIS Viewer for Flex” forum but without a fully satisfying response:
http://forums.arcgis.com/threads/81349-FlexViewer-2.5-MapManager-Error-400?highlight=mapmanager

The workaround with delayed attempts we have implemented on the Viewer <=2.5 solved the problem: the error never reappeared. That’s why we tried to carry out an equivalent modification with viewers >2.5. But having difficulties to do so, and not being the only one to encounter this bug, we thought best to turn to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment