503 error https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer

[TylerJohn]

Hi,

We're currently experiencing a 503 error with the Geocode Service. When using the example below, we consistently encounter this error, particularly when multiple calls are made simultaneously. This tends to happen when approximately 100 calls are made within a 10-second window for a single user. Is there a way to adjust the system to accommodate these simultaneous calls?

2024-05-07 18:31:36.201 ERROR --- [-9003-exec-4002] StackTrace : Full Stack Trace:
java.io.IOException: Server returned HTTP response code: 503 for URL: https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?SingleLine...

Your assistance with this matter would be greatly appreciated, as this issue arises nearly every day.

Best regards,
John

[BradNiemand]

John,

I would like to know more about your workflow.  Why is your application sending 100 findAddressCandidates calls to the service within 10 seconds?  Are you instead really trying to batch geocode a set of addresses?  If you are trying to geocode a table or set of addresses we would recommend that you use the GeocodeAddresses operation instead of findAddressCandidates.  The GeocodeAddresses operation will allow you to submit up to 1000 addresses as a single input and get all of the geocoded results back for those 1000 inputs.

In addition to that, if you will be storing the results in a database you should be using the GeocodeAddresses operation or the findAddressCandidates operation with the forStorage parameter set to true.  This will require a token and will consume credits.  The findAddressCandidates operation with the forStorage parameter set to false (this is the default) is meant to be used for displaying results on the map but not storing them in a database.

Brad

[TylerJohn]

@BradNiemand Thank you for the response

While using the GeocodeAddresses operation would be the ideal and long term solution, we would like to avoid making a code change at this time. Implementing such a change would necessitate re-testing all related features, and we currently lack the resources to do so. Therefore, we are hoping there might be an adjustment in our ESRI account settings that could help resolve this issue.