I don't think so. I'm running a task in Ruby and delaying requests so I won't hit the rate limit. If I did, wouldn't I see a 503 response instead 500? It's very random when I get a 500. Once I got in on my second query, and then another time 50 or so in. This same code was working fine last weekend.
We’ve just deployed the fix for this, you can see our error rate has gone back down to zero: http://note.io/1lIaCSe
Weirdest thing, they did indeed start on September 3 but there was nothing done on our API infrastructure and it only seemed to affect 3 of our 8 HTTP servers. Solution? Restarted the app and everything calmed back down. Gotta love it when those gremlins get in there...
I'm getting some HTTP 500 errors tonight, so I thought I'd re-open. It might be because I'm hitting some limits, but I'm not sure since the API documentation might be a bit outdated in that area.
Dear friends: today I have found this ugly error; the message error was:
Server returned HTTP response code: 500 for URL: https://api.themoviedb.org/3/search/person?api_key=...&language=es&query=Brad&page=3
Exception in thread "main" java.lang.NullPointerException
at fp.tmdb.TMDBAPIImpl.getAllPersonsByName(TMDBAPIImpl.java:221)
at fp.tmdb.test.TestSearch86.main(TestSearch86.java:15)
Archivo no encontrado
Firefox no puede encontrar el archivo en https://api.themoviedb.org/3/search/person?api_key=...&query=Brad&page=3.
Compruebe que el nombre de archivo no tiene errores de escritura, incluyendo el uso de mayúsculas.
Compruebe si el archivo ha sido movido, renombrado o eliminado.
(I am writting from Spain). It's means "File not found" (File???)
The "language=es" is not the problem: it happens the same without it. It looks like the server doesn't like "Brad": the same code works well when asking for "Smith" or "e", with the expectable 429 error code after 40 queries.
I've ommited the api_key here, but not in the queries, of course.
Resposta de Travis Bell
em 6 setembro 2014 às 1:15 AM
Hi Kenton,
No known issues this evening. Is it possible you were hitting our rate limits?
Resposta de Kenton Glass
em 6 setembro 2014 às 3:59 AM
I don't think so. I'm running a task in Ruby and delaying requests so I won't hit the rate limit. If I did, wouldn't I see a 503 response instead 500? It's very random when I get a 500. Once I got in on my second query, and then another time 50 or so in. This same code was working fine last weekend.
Resposta de Samara
em 6 setembro 2014 às 8:24 AM
I've noticed this the last days using different apps, it's very annoying
Resposta de Travis Bell
em 6 setembro 2014 às 11:09 AM
We're looking into this but there is nothing obvious at the moment. I'll update this thread when I have more information.
Resposta de Kenton Glass
em 6 setembro 2014 às 11:19 AM
Thanks, Travis! Could it be related to the API update on 9/4?
Resposta de Travis Bell
em 6 setembro 2014 às 11:54 AM
Hey Kenton,
We haven’t done a deploy on the API since Aug 28 (and there’s no obvious load issues), so we’re not sure what it could be quite yet.
Resposta de ranjhanisaddam
em 6 setembro 2014 às 2:17 PM
I think the problem resides your side because sometimes this error comes and some times it does not...!
Resposta de Travis Bell
em 6 setembro 2014 às 6:09 PM
Hey guys,
We’ve just deployed the fix for this, you can see our error rate has gone back down to zero: http://note.io/1lIaCSe
Weirdest thing, they did indeed start on September 3 but there was nothing done on our API infrastructure and it only seemed to affect 3 of our 8 HTTP servers. Solution? Restarted the app and everything calmed back down. Gotta love it when those gremlins get in there...
Resposta de Kenton Glass
em 6 setembro 2014 às 6:13 PM
So lovely when a restart fixes weirdness. Thanks for looking into and fixing things on a Saturday, Travis!
Resposta de Michell Bak
em 14 setembro 2014 às 6:22 PM
Hi there!
I'm getting some HTTP 500 errors tonight, so I thought I'd re-open. It might be because I'm hitting some limits, but I'm not sure since the API documentation might be a bit outdated in that area.
This says that we'll receive a 503 error if we exceed the request limit (of 30 requests every 10 seconds): http://docs.themoviedb.apiary.io/reference
While this says that we'll receive a 429 error if we exceed the request limit (of 40 requests); https://www.themoviedb.org/documentation/api/status-codes
Can we get some clarification on that? :-)
Resposta de Samara
em 14 setembro 2014 às 7:16 PM
I'm getting this errors, too since this afternoon
Resposta de Travis Bell
em 14 setembro 2014 às 8:57 PM
I just restarted the app like before, can you tell me if they have stopped?
Resposta de Samara
em 15 setembro 2014 às 7:45 PM
seems to be okay
Resposta de Carlos G. Vallejo
em 22 maio 2017 às 1:50 PM
Dear friends: today I have found this ugly error; the message error was:
If you try to go to
https://api.themoviedb.org/3/search/person?api_key=...&language=es&query=Brad&page=3
it appears an even ugglier error: in Firefox:
(I am writting from Spain). It's means "File not found" (File???)
This doesn't happens when I was looking at
https://api.themoviedb.org/3/search/person?api_key=...&language=es&query=Brad&page=2
or
https://api.themoviedb.org/3/search/person?api_key=...&language=es&query=Brad&page=4
The "language=es" is not the problem: it happens the same without it. It looks like the server doesn't like "Brad": the same code works well when asking for "Smith" or "e", with the expectable 429 error code after 40 queries.
I've ommited the api_key here, but not in the queries, of course.
Resposta de Travis Bell
em 23 maio 2017 às 11:06 AM
@vallejo Would you mind creating a new discussion for this? No need to resurrect a 2.5 years old thread