You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: frederik[at]remote.org [Submitted to the original trac issue database at 2.16pm, Friday, 11th May 2007]
When uploading changes from JOSM, on average one in 200 calls fails with "500 internal server error". Immediate retry is then successful.
At one time, I had two parallel uploads running with JOSM, and they both failed at exactly the same time - it may just have been coincidence but may also be a sign of some inter-process or inter-thread problem at the server?
The text was updated successfully, but these errors were encountered:
Author: writetodan[at]yahoo.com [Added to the original trac issue at 1.24pm, Sunday, 13th May 2007]
this ticket on server restarts is probably relevant: #434
as might be this info from Steve on ML:
HTTPISE 500's. The server is running lighthttpd on top of fcgi using
the script/process scripts. These are running with 3 threads with a
restart time of 2 seconds. The threads commit suicide after some
number of requests (which I will increase in a sec) to either the map
or gpx call. When that happens, lightttpd and fcgi are supposed to
pause the queue of requests (which may or may not be api requests).
My suspicion is that the queue is getting killed (and thus a bunch of
500's) instead.
Looking through the logs the rails stuff itself is not producing the
500s, its somwthing to do with the threads killing themselves.
Reporter: frederik[at]remote.org
[Submitted to the original trac issue database at 2.16pm, Friday, 11th May 2007]
When uploading changes from JOSM, on average one in 200 calls fails with "500 internal server error". Immediate retry is then successful.
At one time, I had two parallel uploads running with JOSM, and they both failed at exactly the same time - it may just have been coincidence but may also be a sign of some inter-process or inter-thread problem at the server?
The text was updated successfully, but these errors were encountered: