Send Timeout?

[ChadN]

Hi. I've got DCM4CHEE 5 pushing a single instance to another DICOM node that appears to time out:

2019-10-31 08:45:21,899 INFO  DCM4CHEE->EVERCORE(2046) << A-ASSOCIATE-RQ
2019-10-31 08:45:22,071 INFO  DCM4CHEE->EVERCORE(2046) >> A-ASSOCIATE-AC
2019-10-31 08:45:22,555 INFO  DCM4CHEE->EVERCORE(2046) << 1:C-STORE-RQ[pcid=3, prior=0
  cuid=1.2.840.10008.5.1.4.1.1.7 - Secondary Capture Image Storage
  iuid=1.XXX - ?
  tsuid=1.2.840.10008.1.2.1 - Explicit VR Little Endian
2019-10-31 08:46:21,916 INFO  DCM4CHEE->EVERCORE(2046) >> A-RELEASE-RQ
2019-10-31 08:46:21,916 INFO  DCM4CHEE->EVERCORE(2046) << A-RELEASE-RP
2019-10-31 08:46:21,978 INFO  DCM4CHEE->EVERCORE(2046): close Socket[addr=hostname/192.xxx.xxx.xxx,port=4000,localport=50702]
2019-10-31 08:46:43,440 WARN  DCM4CHEE->EVERCORE(2046): failed to send Instance[iuid=1.XXX,cuid=1.2.840.10008.5.1.4.1.1.7] to EVERCORE

Is there a 1 minute timeout anywhere that I can increase?

I'm not totally convinced that is the issue, as after this fails, I can attempt the C-STORE again and it works within less than 15 seconds. Still, if I could increase a timeout it would be an easy test, but all of the timeouts I see in the configuration are set to blank (infinite). 

Thanks,

-C

[Gunter Zeilinger]

According the log it rather looks that the other side (EVERCORE) sends the A-RELEASE-RQ, not DCM4CHEE!

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

--

You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/3282ac5c-abd8-4daa-b5d4-b9adf94d8878%40googlegroups.com.

[ChadN]

Ah. I should have paid more attention to the direction of the arrows!

Thanks, I'll pursue them further.

-C 

[Alvaro G [Andor]]

Hi,

Without knowing your network, my theory would be the EVERCORE is looking for the studies on a slow/secondary storage, o requesting them to a remote PACS.

• First time, it's looking for it, timeouts, kicks you out.
• Second time, the study is already on the cache or local storage, and you get it quickly.

Regards,

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/015ca0cc-02d2-4d9b-8b60-4161011d7d43%40googlegroups.com.

[ChadN]

That's great insight, Andor. I'm working with the Evercore guys to look at increasing their own timeouts.

I also notice that when I download the offending instance in DCM4CHEE 5, it takes a while to copy it to its web cache before download (the single instance is ~160MB). The second time, it comes very quickly, since the file is already cached. 

Could something similar be happening on C-STORE on my end? 

Thanks,

-C

On Thursday, October 31, 2019 at 3:25:43 PM UTC-5, andor wrote:

Hi,

Without knowing your network, my theory would be the EVERCORE is looking for the studies on a slow/secondary storage, o requesting them to a remote PACS.

• First time, it's looking for it, timeouts, kicks you out.
• Second time, the study is already on the cache or local storage, and you get it quickly.

Regards,

On 10/31/19 9:18 PM, ChadN wrote:

Ah. I should have paid more attention to the direction of the arrows!

Thanks, I'll pursue them further.

-C 

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm...@googlegroups.com.