I know there was a small race condition that could lead to having one request being handed to multiple clients.
(Although in most cases I followed up, a client had just handed back a job to the server and another one had instantly grabbed it) This is likely what happened if the job doesn't appear on your user page anymore. I have now implemented database transactions and locked the request row that is being handed to a client with "SELECT ... FOR UPDATE". Let me know if you are still seeing a request being worked on by multiple clients (but make sure it has not been returned to the server by one client already, which is not that easy to spot, especially in forked render mode). spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
