When JaSPer POSTs a contest XML file, IACCDB currently saves the file, returns an HTTP 200 response code, and starts a background job to process the data. Unfortunately, there are a myriad of things that can go wrong during background processing and no mechanism to report them to anyone.
Make the processing synchronous, i.e. running in the foreground. Downside: This may take a few minutes during which JaSPer would presumably be frozen, and a timeout is also needed to ensure that it doesn't stay stuck forever.
Report to me, and/or Bwana, and/or the contest director via email or text if background processing fails.
When JaSPer POSTs a contest XML file, IACCDB currently saves the file, returns an HTTP
200
response code, and starts a background job to process the data. Unfortunately, there are a myriad of things that can go wrong during background processing and no mechanism to report them to anyone.