[BitBucket user: Derek Merck]
[BitBucket date: 2018-07-28.18:21:19]

Using `jodogne/orthanc:1.4` docker image on a recent Debian Stretch Vagrant box.

1. Run 2 orthanc containers, source and target, that register one another as peers
2. Load a study into source, send it to target peer through UI -> success
3. Resend study to target peer -> failure after about 15 slices are sent
4. Send study from target back to source peer -> failure after about 15 slices are sent
5. Load another study into source (or create a new one by anonymizing the first), send it to target peer -> success
6. Resend new study to target peer -> failure after about 15 slices are sent

Sender reports an "HTTP status 0" in logs (which appears to actually be a 500 in the page headers?) No reference to the failure in the receivers logs, just the 15ish successful receipts.

Same sequence using DICOM modality sends succeeds.

Same sequence with docker image using recent build from source fails.

Same sequence with `jodogne/orthanc:1.3.2` image succeeds.

My suspicion based on narrowing it down to resends on the new threaded version is that the worker threads are able to keep up with new studies, but not with resends, which appear in the logs to also require file deletes.  So eventually the scheduler runs out of workers, makes the sender wait, and the sender immediately gives up.

Let me know if it would be helpful to have more details about my setup to reproduce.

Thanks again for your continuing work on this -- it is an amazing piece of open source software!

[Bugzilla user: narsimha.kuna@circlecvi.com]
[Bugzilla date: 2021-05-06T11:42:13+00:00]

1. Un installed Orthanc 1.7.1
2. Removed C:\Program Files\Orthanc Server folder
3. Removed C:\Orthanc folder
4. Re-started the system
5. Installed 1.9.2
6. Re-started the system
7. C:\Users\kunan>curl http://localhost:8042/modalities?expand
{}
8. C:\Users\kunan>curl -v -X PUT http://localhost:8042/modalities/sample -d '{"AET" : "ORTHANCC", "Host": "127.0.0.1", "Port": 2002}'
*   Trying ::1...
* TCP_NODELAY set
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 8042 (#0)
> PUT /modalities/sample HTTP/1.1
> Host: localhost:8042
> User-Agent: curl/7.55.1
> Accept: */*
> Content-Length: 5
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 5 out of 5 bytes
< HTTP/1.1 400 Bad Request
< Connection: keep-alive
< Keep-Alive: timeout=1
< Content-Length: 196
<
{
        "HttpError" : "Bad Request",
        "HttpStatus" : 400,
        "Message" : "Bad file format",
        "Method" : "PUT",
        "OrthancError" : "Bad file format",
        "OrthancStatus" : 15,
        "Uri" : "/modalities/sample"
}
* Connection #0 to host localhost left intact
* Bad URL, colon is first character
* Closing connection -1
curl: (3) Bad URL, colon is first character
* Rebuilt URL to: ORTHANCC,/
* Could not resolve host: ORTHANCC,
* Closing connection 1
curl: (6) Could not resolve host: ORTHANCC,
* Rebuilt URL to: Host:/
* Could not resolve host: Host
* Closing connection 2
curl: (6) Could not resolve host: Host
* Rebuilt URL to: 127.0.0.1,/
* Connection 0 seems to be dead!
* Closing connection 0
* Could not resolve host: 127.0.0.1,
* Closing connection 3
curl: (6) Could not resolve host: 127.0.0.1,
* Rebuilt URL to: Port:/
* Could not resolve host: Port
* Closing connection 4
curl: (6) Could not resolve host: Port
curl: (3) [globbing] unmatched close brace/bracket in column 5

9. not able to add new modality using REST API

[Bugzilla user: s.jodogne@gmail.com]
[Bugzilla date: 2021-05-06T11:51:19+00:00]

NK's entry has nothing to do with the original issue, is *not* a bug, and is discussed here:
https://groups.google.com/g/orthanc-users/c/wSsKw5vohCE/m/vIu1qIrRBAAJ

DO NOT TAKE it into consideration.

(In reply to NK from comment #1)

[Bugzilla user: s.jodogne@gmail.com]
[Bugzilla date: 2021-06-25T06:59:38+00:00]

Thanks for the report. I am personally unable to reproduce your issue, probably because it refers to an old version of Orthanc (1.4.0 that is 3 years old), whereas we are at Orthanc 1.9.4 at the time of writing.

I am thus closing this issue for now. Don't hesitate to re-open it if you can provide a minimal working example for us to reproduce your issue using a up-to-date version of Orthanc:
https://book.orthanc-server.com/users/support.html#discussing-a-minimal-working-example