Check report size before transfer attempt
Reports bigger then 16MB are stuck in transfer folder, resulting in a growing pending queue and blocking regularly sized reports from being transferred. I believe such reports should be rejected and moved to a separate subfolder without an attempt at transfer, since we know they won't be transferred anyway.
-
Hi Bogna,
With which version of the client have you seen this?
In the newest 5.1 client (5.1.92), when the WATS server rejects a report or something goes wrong during a transfer, the client changes the report file's extension to .Error. Since the client only looks for files with file extension .Queued when looking for reports to submit, it ignores the failed report(s). When a report has had .Error as its file extension for about 5 minutes, it is changed back to .Queued and an attempt to transfer it will be made shortly after.
-
Hi Anders,
I am not 100% sure, since I did a lot of upgrades since then, but I'm quite sure last time I saw that behavior it was on 5.1.0.84.
However, the description of 5.1.92 behavior does not sound like a solution to this problem, but rather it's cause.
Reports larger than 16MB are always rejected by the server ("Request entity too large"), so they get stuck in this Queued -> Error -> Queued circle. There is no way that they would eventually get accepted by server, because they violate a primary rule. And while the WATS Client is occupied with attempts to send the large files over and over again, properly-sized reports are stuck in the queue behind the large ones.
Hence I believe that reports larger than 16MB should be permanently removed from the queue folder, not renamed and waiting for next attempt to be transferred. -
Hi Bogna,
I have confirmed now that with the 5.1 client we do not have a limit on 16MB reports. We do have a limit on 4.2 clients. The reason you get "Request entity too large" with the 5.0 or 5.1 clients must have something to do with the specific server setup (the WATS application doesn't set a limit, but someone could configure the server itself to have one), or the specific network setup.
Still, there are certain errors where we know the report will never be uploaded. "Request entity too large" should be one of them (unless server settings are changed). When catching such an error, the client could not add the report back in the queue, and instead put it somewhere else.
Please sign in to leave a comment.
Comments
3 comments