search

rbeckman-nextgen / test-mc3

0 stars 0 forks source link

Mirth Connect DICOM Destination doesn't break up far enough to report failure of DICOM message #4315

Open rbeckman-nextgen opened 4 years ago

rbeckman-nextgen commented 4 years ago
  1. Image was sent to a DICOM receiver.
  2. Receiver responded with the following message ` ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: ERROR: Received RSP with Status 0110H for /tmp/mirthconnect/temp2189851785041387890tmp, cuid=1.2.840.10008.5.1.4.1.1.7, tsuid=1.2.840.10008.1.2.1 ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: (0000,0002) UI #26 [1.2.840.10008.5.1.4.1.1.7] Affected SOP Class UID ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: (0000,0100) US #2 [32769] Command Field ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: (0000,0120) US #2 [1] Message ID Being Responded To ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: (0000,0800) US #2 [257] Command Data Set Type ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: (0000,0900) US #2 [272] Status ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: (0000,0902) LO #32 [Store Exception: Unable to store] Error Comment ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server: (0000,1000) UI #48 [1.3.6.1.4.1.50144.1.2.REDACTED] Affected SOP Instance UID ERROR 2019-09-25 10:10:32,855 [DCMSND-3237718] Server:

`

  1. Even though there was an error in the logs, the dcm4che lib did catch the error, but it didn't escalate to report the message as failed, as it reported the message to Mirth as successfully being sent.

Imported Issue. Original Details: Jira Issue Key: MIRTH-4460 Reporter: brianda Created: 2019-09-26T10:59:05.000-0700