problem

If a user session was removed due time out or log out, the task used by the user in that session is still locked. (Unless the user has left the task before).

If he just closes the browser or is getting logged out (via API / embedded translate5) the task remains locked.

A clean up of that orphaned locks is performed on each task listing (GET /editor/task). This was fine for GUI usage, but for API usage and usage of the editor in direct access this clean up must be done more often!

solution

Possible solution: Clean up wie cron, like the done workers are clean uped.

Unify garbage collections via cron (enabled by configuration), by default as it is invoked currently.

The following clean up functions should be affected:

• ZfExtended_Resource_Session::garbageCollector
• editor_Models_TaskUserAssoc::cleanupLocked
• editor_Models_Task::cleanupLockedJobs
• Zf_worker::cleanGarbage

Cronjob

The cronjob can be triggered via HTTP call to URL:

http://translate5.example.org/editor/cron/periodical

If the URL is called once, the application is reconfigured, so that the default request based cleanup is deactivated.