# Response Code 503 showing in application **URL:** \ **Category:** APM\ **Tags:** rum, server\ **Created:** [February 10, 2020, 9:26am UTC](https://discuss.elastic.co/t/response-code-503-showing-in-application/218549 "2020-02-10T09:26:01Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rijash](https://avatars.discourse-cdn.com/v4/letter/r/c2a13f/32.png) [@rijash](https://discuss.elastic.co/u/rijash)\ **Post date:** [February 10, 2020, 9:26am UTC](https://discuss.elastic.co/t/response-code-503-showing-in-application/218549/1 "2020-02-10T09:26:02Z")
Hi, Application is showing response Code " **503**" for RUM events ( (/intake/v2/rum/events) whenever we are seeing " **Queue is Full**" message in APM Server. As per our understanding, If the server is not able to process the event it will be lost & not impact the application availability. Could you please help to address the issue. **Elasticsearch version** : 7.4.0 **APM Server version** : 7.4.0 **APM Agent language and version** : 1.9.0 Regards, Rijash ---
**Author:** ![Hamidreza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hamidreza/32/21369_2.png) [@Hamidreza](https://discuss.elastic.co/u/Hamidreza)\ **Post date:** [February 10, 2020, 12:40pm UTC](https://discuss.elastic.co/t/response-code-503-showing-in-application/218549/2 "2020-02-10T12:40:40Z")
Hi @rijash, Thanks for reaching out. The RUM agent sends the queued events to the APM server in a single requests and clears the queue regardless of whether APM server was able to process those events. Making a request to the APM server is the only way the agent can know if the server is able to process the request or not. This should not affect the availability of your application since these events are sent via a separate asynchronous http request. Would you please explain a bit more, in what way the failing requests affect your application? Cheers, Hamid ---
**Author:** ![rijash](https://avatars.discourse-cdn.com/v4/letter/r/c2a13f/32.png) [@rijash](https://discuss.elastic.co/u/rijash)\ **Post date:** [February 10, 2020, 12:56pm UTC](https://discuss.elastic.co/t/response-code-503-showing-in-application/218549/3 "2020-02-10T12:56:29Z")
Hi Hamid, Thank you for your prompt response here. We are getting the below error log in in application server. 10.8.248.10 71.75.17.36, 10.8.248.10 - - [07/Feb/2020:18:24:05 -0500] "POST /intake/v2/rum/events HTTP/1.1" **503** 568 Regards, Rijash ---
**Author:** ![rijash](https://avatars.discourse-cdn.com/v4/letter/r/c2a13f/32.png) [@rijash](https://discuss.elastic.co/u/rijash)\ **Post date:** [February 10, 2020, 12:58pm UTC](https://discuss.elastic.co/t/response-code-503-showing-in-application/218549/4 "2020-02-10T12:58:18Z")
We are routing the RUM events captured for the application to APM server via nginx server. ---
**Author:** ![Hamidreza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hamidreza/32/21369_2.png) [@Hamidreza](https://discuss.elastic.co/u/Hamidreza)\ **Post date:** [February 11, 2020, 1:02pm UTC](https://discuss.elastic.co/t/response-code-503-showing-in-application/218549/5 "2020-02-11T13:02:19Z")
The error log information is only there for your information. This error simply means that APM server (or Elasticsearch instance) can not handle the load and requires more resources. Since the APM components function independent from your application this shouldn't affect your application. However, it is recommended to either increase the resources on your servers or adjust the [`transactionSampleRate`](https://www.elastic.co/guide/en/apm/agent/rum-js/current/configuration.html#transaction-sample-rate) in the RUM agent configuration to avoid this error. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 3, 2020, 9:02am UTC](https://discuss.elastic.co/t/response-code-503-showing-in-application/218549/6 "2020-03-03T09:02:30Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.