Closed palmerj closed 11 years ago
Did something like that in the last commit but the problem now is OGRError: General Error. Another instance of enabling exception now catching errors that weren't otherwise a problem. And the 504's recur, at least with v:x772
Implemented, though gdal.GetLastErrorMsg() seems to be less reliable than reading RuntimeErrors for getting crash information. Also added some retry code initialising a new source (LDS) DS. Looks as if the root cause is 504 or at least some kind of server originating problem and isn't going to be easily addressed client side.
Within the feature loops in the featureCopyIncremental and featureCopy DataStore methods it would be a good idea to trap HTTP 504 errors and potentially re-entry (be careful to roll-back the transaction first). Here's some code that generically traps OGR exceptions: