Open dmedv opened 8 years ago
Is there a full stack trace?
No. Exception stack trace in TransferThread is currently logged only using ex.printStackTrace(), and looks like Tomcat is not set up to redirect stdout to catalina.out... I need some time to figure out how it's done, or maybe we should fix the logging, because using ex.printStackTrace for logging is probably not a very good idea anyway.
Doesn't get stuck anymore, but still not working properly because of incorrect SWIFT setup. SWIFT is returning "500 Not found" errors when trying to delete existing files. Should be fixed.
Swift setup has been fixed. Needs testing.
Same behavior. And the 409 errors are still there. Honestly, it's very unlikely that someone will repeat this action, so I will remove the showstopper label, to show that this is not highest priority.
I have tried moving a few files back and forth between two panels (several files at once). Eventually SciDrive got stuck, with unprocessed RabbitMQ messages accumulating and HTTP 409 errors in the log:
ERROR edu.jhu.pha.vospace.jobs.TransferThread - Error executing job 9ee77108-9eef-4c8c-8ee1-74c49c61e8a0: edu.jhu.pha.vospace.api.exceptions.ConflictException: HTTP 409 Conflict
I could reproduce this problem after restarting Tomcat and RabbitMQ and doing the same operations for some time (takes a few minutes of moving files back and forth)...