Hi there,
We have some dockerized applications generating large logs, i.e. 5-10MB, and XNAT CS is -sometimes- unable to collect logs as files for those cases.
When using the REST API for fetching them manually -again this occurs sporadically but not always- XNAT returns a 500 status code with the following message,
'java.lang.RuntimeException: org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected'
I wonder if -due to the log size- there is an unexpected behaviour behind the scenes, perhaps XNAT closes the connection with the HTTP client when log content is still being transmitted or similar?
Bear in mind that container logs are formally stored by Docker using the
by-default logging driver (that is, as JSON files) which increases considerably its size and so does -I presume- the work to collect/read them by the XNAT API
.
For now I have defined a retry strategy to effectively fetch them via API calls but I wonder if there's something on the server side that could be adjusted for ensuring the proper collection of stdout/stderr log files.
Thanks,
Jordi