Issue61

Title Large files fail to be uploaded (at least from OsiriX)
Priority feature Status resolved
Superseder Nosy List admin
Assigned To
Keywords Orthanc Core

Created on 2017-08-07.12:00:46 by admin, last changed by admin.

Messages
msg281 (view) Author: admin Date: 2017-08-07.12:00:46
[BitBucket user: Oskar Bożek]
[BitBucket date: 2017-08-07.10:00:46]

Studies with very large single files - around 500 MB - in my cases from fluoroscopy fail to upload without any significant error - disk write too slow? 
I will try to provide anonymous dataset upon request.
msg282 (view) Author: admin Date: 2017-08-07.22:54:12
[BitBucket user: Sébastien Jodogne]
[BitBucket date: 2017-08-07.20:54:12]

Hello, indeed, we need sample data to be able to reproduce this issue. Are you sure to be using a 64bit version of Orthanc? What is the content of the [Orthanc log](book.orthanc-server.com/faq/log.html)?
msg283 (view) Author: admin Date: 2017-08-12.20:41:30
[BitBucket user: Oskar Bożek]
[BitBucket date: 2017-08-12.18:41:30]

Unfortunately the fluoroscopy machine got broken a few days ago, and the data I have contains burnt-in patient data. I'll try to reproduce it again and check the orthanc log, but I suppose it was this error, yet I need to check it again:
E0803 09:53:27.349645 CommandDispatcher.cpp:908] DIMSE failure (aborting association): DIMSE No data available (timeout in non-blocking mode)
msg284 (view) Author: admin Date: 2018-03-07.14:42:23
[BitBucket user: Sébastien Jodogne]
[BitBucket date: 2018-03-07.13:42:23]

Putting this issue "on hold", given the absence of feedback. Don't hesitate to reactivate it once you can provide the requested information.
msg285 (view) Author: admin Date: 2019-01-25.10:03:47
[BitBucket user: Sébastien Jodogne]
[BitBucket date: 2019-01-25.09:03:47]

Any news about this issue? In the absence of answer, I'll soon close it.
msg286 (view) Author: admin Date: 2019-01-26.20:25:59
[BitBucket user: Oskar Bożek]
[BitBucket date: 2019-01-26.19:25:59]

We abandoned orthanc in this enviroment, although I could provide adequate test data. 
Anyway - I'm pretty sure it was a simple timeout which could have been fixed by adjusting the adequate parameters. The acquisition device provides (and interally somehow handles) surprisingly huge files, our top size is currently over 20 GB (single video sequence).
msg287 (view) Author: admin Date: 2019-01-27.15:46:02
[BitBucket user: Sébastien Jodogne]
[BitBucket date: 2019-01-27.14:46:02]

OK, fine, thanks for the feedback. As the issue can theoretically be solved by increasing timeouts, I close it now.
History
Date User Action Args
2026-07-29 15:51:21admincreate