Citizen Service Request - "_577: Timeout exceeded"

4738
1
Jump to solution
08-22-2014 12:51 PM
Labels (1)
JoshVan_Kylen
New Contributor III

Whenever I attempt to upload a large file after about 3 minutes in the console I get the message:

_577: Timeout exceeded {message: "Timeout exceeded", response: Object, status: undefined, responseText: undefined, xhr: XMLHttpRequest…}_ssl: undefinedlog: undefinedmessage: "Timeout exceeded"response: ObjectresponseText: undefinedstack: (...)get stack: function () { [native code] }set stack: function () { [native code] }status: undefinedxhr: XMLHttpRequest__proto__: TMP init.js:15_49d init.js:15(anonymous function) init.js:15_1e1 init.js:15_1df init.js:15resolve.callback init.js:15_1e1 init.js:15_1df init.js:15reject.errback init.js:15_1e1 init.js:15_1df init.js:15reject.errback init.js:15_1e1 init.js:15_1df init.js:15reject.errback init.js:15(anonymous function) init.js:15_4c2 init.js:15_4bc init.js:15_4da.reject init.js:15_4c8 init.js:15_4c2 init.js:15_4bc init.js:15_4da.reject init.js:15_4c8 init.js:15_4c2 init.js:15_4bc init.js:15_4da.reject init.js:15_4c8 init.js:15_4c2 init.js:15_4bc init.js:15_4da.reject init.js:15_4c8 init.js:15_4c2 init.js:15_4bc init.js:15_4da.reject init.js:15cancel._4cf.cancel init.js:15_520 init.js:15

Does anyone have any suggestion on how to prevent this error and allow users to wait as long as they like to upload there large video files?

It appears to be occurring in the "SubmitIssueDetails" function I'm almost certain it is on this line:

map.getLayer(serviceRequestLayerId).addAttachment(addResults[0].objectId, dojo.byId('formFileUpload'), function (sucess)

My previous thread on a  similar topic appears to solve the maximum file size limitation.

https://community.esri.com/message/353283?sr=search&searchId=dd718e63-9b94-4195-a883-04570113e114&se...

Any help will be greatly appreciated.

0 Kudos
1 Solution

Accepted Solutions
LuigiManco
New Contributor

I solved this issue by increasing the maximum number of instances for the service

View solution in original post

1 Reply
LuigiManco
New Contributor

I solved this issue by increasing the maximum number of instances for the service