Internal client exception Read timed out

User Service
1

Hi.

I have started seeing a behavior in my log in operation. Often, nothing happens and after about 5 min I recieve:

Internal client exception Read timed out from the “handleFault” method of the login operation.

What I wonder is if this is caused by reaching the limitation of some parameter on Backendless, max API call or similar? I haven’t really learned how the Analytic part of Backendless works yet.
Thanks!

2

Hello B.Bolgakov,

What SDK do you use?

Artur.

3

Android-SDK

4

Please post here the code snipped what causes error. Please use github gist.
And also specify the Backendless type you use, Online or Standalone?
Artur.

5

I use the Online type.

6

Hello,
Your code seems legal. The error you receive tells that your client device can not access Backendless server.
Did you try request to another Backendless service?
Did you try to perform any HTTP actions from the device (It may be connection issues)?
Artur.

7

Not sure what you mean by “another Backendless service” ?
Yes all other HTTP actions work, there’s nothing wrong with my network/connection.

What I can add to this is, sometimes when doing Backendless.Persistence.save() it too “freezes” like the login operation. It’s not always , but pretty regulary.

8

Hello,
I meant Persistence, or any other service.
There should be connection issues. Please look at the related ticket http://support.backendless.com/t/response-speed-in-spain-is-too-slow-any-solution, and repeat steps made there.
Artur.

9

“PING horsesrv-225955670.us-east-1.elb.amazonaws.com (107.23.223.155) 56(84) bytes of data.” from ping

"traceroute to api.backendless.com (52.0.85.19), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.159 ms 0.153 ms 0.171 ms
2 c213-200-142-147.bredband.comhem.se (213.200.142.147) 7.845 ms 7.852 ms 8.352 ms
3 213.200.166.165 (213.200.166.165) 9.194 ms 9.478 ms 9.500 ms
4 nap-core-1-be112.net.comhem.se (213.200.163.91) 13.030 ms 13.432 ms 13.419 ms
5 212.73.250.17 (212.73.250.17) 12.544 ms ae61.edge3.Stockholm2.Level3.net (213.242.69.201) 12.558 ms 16.499 ms
6 * * *
7 AMAZON.COM.edge1.Washington1.Level3.net (4.28.125.110) 116.006 ms 117.669 ms 117.772 ms
8 * * *
9 * * *
10 54.239.110.249 (54.239.110.249) 1380.003 ms 54.239.110.233 (54.239.110.233) 1379.948 ms 54.239.110.245 (54.239.110.245) 1361.319 ms
11 54.239.111.75 (54.239.111.75) 120.010 ms 54.239.111.79 (54.239.111.79) 119.106 ms 54.239.109.111 (54.239.109.111) 119.945 ms
12 205.251.244.189 (205.251.244.189) 118.544 ms 205.251.244.193 (205.251.244.193) 119.432 ms 72.21.222.129 (72.21.222.129) 118.749 ms
"
from traceroute

10

What is the output of ping?

11

Here:
PING horsesrv-225955670.us-east-1.elb.amazonaws.com (107.23.223.155) 56(84) bytes of data.

12

Ping usually shows latency. Does it produces something more than the first line?

e.g.
PING horsesrv-225955670.us-east-1.elb.amazonaws.com (107.23.223.155) 56(84) bytes of data.
64 bytes from ec2-107-23-223-155.compute-1.amazonaws.com (107.23.223.155): icmp_seq=1 ttl=44 time=170 ms
64 bytes from ec2-107-23-223-155.compute-1.amazonaws.com (107.23.223.155): icmp_seq=2 ttl=44 time=116 ms
64 bytes from ec2-107-23-223-155.compute-1.amazonaws.com (107.23.223.155): icmp_seq=3 ttl=44 time=114 ms

13

If it’s to any help this is what logcat is spitting out when I process the login: https://gist.github.com/progrmor/e72ae5c4a967afa7af36093da88a98c4

No the ping doesn’t produce anything else. No idea why.

14

It actually appears to happen on all Backendless actions. Deleting files also proved to get stuck sort of. Sometimes, I noticed now when trying to delete an image, it get’s “stuck” or keeps loading for about 3-5 min and then it succeeds. So it’s extremely unpredictable. That too gives me “ERROR:BackendlessFault code: ‘Internal client exception’, message: ‘Read timed out’”

15

From what country do you try to access Backendless?

16

Sweden

17

Your IP please

18

192.168.0.16

19

External IP please

http://whatismyipaddress.com/

20

83.255.199.235