Read timed out error after the new deployment of code

Posted by anu31221@gmail.com on 12-Jun-2016 22:52

I am seeing Read timed out while manually creating the lead or through API call.

All Replies

Posted by murali on 12-Jun-2016 23:16

Hi. What is the tenant ID?
 

Posted by murali on 13-Jun-2016 01:26

Hi Anu,
                Around 22:55 CT, there was a concurrent DB backup happening. It might have slowed down the DB service. We are following up with the infrastructure provider. Are you still facing issues or was it only then?

Posted by anu31221@gmail.com on 13-Jun-2016 11:50

We keep seeing the issue. Right now happening for most of the API calls , Below are time I have tried sending the request.

Customer ID

100109106

06/13/2016, 12:37 PM PROD1 SocketTimeoutException Read timed out

06/13/2016, 12:34 PM PROD1 SocketTimeoutException Read timed out

06/13/2016, 12:31 PM PROD1 SocketTimeoutException Read timed out

06/13/2016, 10:36 AM PROD1 SocketTimeoutException Read timed out

06/13/2016, 12:22 AM PROD1 SocketTimeoutException Read timed out

06/13/2016, 12:19 AM PROD1 SocketTimeoutException Read timed out

06/13/2016, 12:09 AM PROD1 IllegalArgumentException Illegal request method null

06/13/2016, 12:07 AM PROD1 IllegalArgumentException Illegal request method null

06/12/2016, 11:59 PM PROD1 IllegalArgumentException Illegal request method null

Posted by murali on 14-Jun-2016 07:16

OK. Will investigate.

Posted by anu31221@gmail.com on 14-Jun-2016 13:05

Please let me know if found the solution. I am seeing this error while creating the record from UI and API

You can call me(201-780-3691) if we need to do screen share.

Posted by murali on 14-Jun-2016 14:22

Hi Anurag,
                Is there an outgoing HTTP call in a create/update trigger?

Posted by murali on 14-Jun-2016 15:29

Anurag, we have figured it out. The  tImeout is from a  HTTP  call from a trigger you have written. The external http service that you are using probably has an issue. Can you check?

Posted by anu31221@gmail.com on 15-Jun-2016 21:21

Do we need more detail to resolve the issue?

Posted by murali on 27-Jun-2016 06:45

Fixed on 6/23

This thread is closed