I have finally had the time to build in a timeout for OSM Route Manager and History Viewer.
Previously, the only limit was the memory of the Java process, which caused some requests to take really really long. The queue got very long and the service became unusable. (And before that, there hadn’t even been a memory limit, the service would just dump cached items from the memory and re-fetch them from the API when needed.)
Now, I have set the timeout to 10 minutes. I know that this might not be enough for the “Relation blame” of medium to big relations, but at least it keeps the service usable.
Comment from seav on 19 May 2011 at 15:08
Thank you very much for implementing the timeout!