1

Resolved

Queued results do not always make it back to the server

description

The client queues results and outgoing files in the event that the server is not reachable when a batch ends. Sometimes when the server re-appears the queue item is discarded by the server or the client fails to send it. I think this is related to a race-condition of sorts.
 
Proposed solution: moving to an embedded database with better data persistence and locking should eliminate this issue.

comments

joes wrote May 13, 2008 at 3:48 PM

"unknown" results are stored in the "unknown" folder and given a random directory name. This isn't ideal, but it guarantees that the server successfully receives all data. Coupled with the persistent xml files, there should be no more issues of losing batch results.

wrote May 13, 2008 at 3:48 PM

wrote Feb 1, 2013 at 3:35 AM

wrote May 14, 2013 at 5:44 AM

wrote May 14, 2013 at 5:44 AM

wrote Jun 4, 2013 at 12:55 AM