Add timeout to DICOM QR SCU

[Ed McDonagh]

Against one QR SCP the process has got stuck a few times, not sure why.

There should be a failsafe that if a process takes too long it is killed.

Retry would be nice, continue with error logged otherwise.

[Jamie Robinson]

Hi Ed,

My QR SCP almost always gets stuck on 0.7.13b whenever I am querying for DX data. Works fine for CT, MG

[Ed McDonagh]

How does it get stuck - do you get any clues?

With my PACS there is a limit on the number of responses that are allowed, and if the query exceeds that then it returns nothing. I can see this in the openrem_qr.log where I would get a handful of results for DX (our newer mobiles), but nothing for CR (our DX fixed room kit, along with real CR).

I was wondering if you had looked at that log for the other email you sent too...

[Jamie Robinson]

I query DX from today - Responses so far updates as expected until around 40 hits (1 Unknown; 26 DX; 16 SR;DX) whereby it hangs with no further updates. Things are currently working fine for CT (with delete settings to no) and I have just queried and moved 64 studies. openrem_qr.log shows

[04/May/2016 12:00:23] INFO [remapp.netdicom.qrscu:33] Association response received [04/May/2016 12:00:24] INFO [remapp.netdicom.qrscu:33] Association response received

No real clues

[Tim de Wit]

Sounds like qrscu crashes somehow instead of getting stuck. What does Celery's default.log say?

[Ed McDonagh]

QR now has much better logging than it did in 2015 (especially in 1.0), so closing this for now and if there is reason to reopen it we can.