PDUException: Received A-ABORT in sending from flouroscopy to PACS

1,599 views
Skip to first unread message

Algie Rosario

unread,
Dec 15, 2014, 1:19:12 AM12/15/14
to

Hi ! Im sending a preset images from flouroscopy to Pacs.

When i try to send 1 image, its successful. But when sending split images (procedure used by the radiologist) it logs this error..

Please see attached file for the screenshot log.




















Thanks and Best Regards

Algie Rosario

unread,
Dec 16, 2014, 12:28:18 AM12/16/14
to dcm...@googlegroups.com
Please help above problem

AJ

unread,
Dec 16, 2014, 12:31:22 AM12/16/14
to dcm...@googlegroups.com
I have the same problem as well

Noong Lunes, Disyembre 15 2014 14:19:12 UTC+8, si Algie Rosario ay sumulat:

gunterze

unread,
Dec 16, 2014, 2:10:47 AM12/16/14
to dcm...@googlegroups.com
According the attached log, the A-ABORT is sent by the Storage SCU, after the PACS accepted the association by sending an A-ASSOCIATE-AC. The screenshot does not show the time, when the A-ASSOCIATE-AC was returned to the Storage SCU, so I cannot see, if the modality aborted the association immediately after receiving the A-ASSOCIATE-AC or after some idle time. Anyway, you have to debug the problem on the Storage SCU.

gunter

Algie Rosario

unread,
Dec 16, 2014, 6:02:21 AM12/16/14
to
Hi Gunter,

Thank you for time to answer the question. I just have read the schimadzu conformance statetement and compare their accepted transfer syntaxes to the  latest dcm4chee conformance statement (Version: 2.X) and its the same.

Regarding to your answer i did change the SERVICE=>StgCmtScuScp=>AcceptedTransferSyntax (added here the ExplicitVRBigEndian) and also the DIMSETimeout (set to 0).

Am i doing the right thing? Thanks

Also heres the log :

2014-12-16 16:12:34,741 INFO  -> (TCPServer-1-1) [org.dcm4cheri.server.ServerImpl] handle - Socket[addr=/192.168.9.240,port=1175,localport=11118]
2014-12-16 16:12:34,741 INFO  -> (TCPServer-1-1) [org.dcm4cheri.net.FsmImpl] Socket[addr=/192.168.9.240,port=1175,localport=11118]
2014-12-16 16:12:34,757 INFO  SDR100_STORE_SCU->dcmPACS (TCPServer-1-1) [org.dcm4cheri.net.FsmImpl] received AAssociateRQ
appCtxName: 1.2.840.10008.3.1.1.1/DICOM Application Context Name
implClass: 1.2.392.200036.9110.1.0.6711.2001002
implVersion: SPF 6.0.0
calledAET: dcmPACS
callingAET: SDR100_STORE_SCU
maxPDULen: 16384
asyncOpsWindow:
pc-1: as=1.2.840.10008.1.1/Verification SOP Class
ts=1.2.840.10008.1.2.1/Explicit VR Little Endian
ts=1.2.840.10008.1.2/Implicit VR Little Endian
ts=1.2.840.10008.1.2.2/Explicit VR Big Endian
pc-3: as=1.2.840.10008.5.1.4.1.1.12.2/X-Ray Radiofluoroscopic Image Storage
ts=1.2.840.10008.1.2.1/Explicit VR Little Endian
ts=1.2.840.10008.1.2/Implicit VR Little Endian
ts=1.2.840.10008.1.2.2/Explicit VR Big Endian
2014-12-16 16:12:34,757 INFO  SDR100_STORE_SCU->dcmPACS (TCPServer-1-1) [org.dcm4cheri.net.FsmImpl] sending AAssociateAC
appCtxName: 1.2.840.10008.3.1.1.1/DICOM Application Context Name
implClass: 1.2.40.0.13.1.1.1
implVersion: dcm4che-1.4.31
calledAET: dcmPACS
callingAET: SDR100_STORE_SCU
maxPDULen: 16352
asyncOpsWindow:
pc-1: 0 - acceptance
ts=1.2.840.10008.1.2/Implicit VR Little Endian
pc-3: 0 - acceptance
ts=1.2.840.10008.1.2/Implicit VR Little Endian
2014-12-16 16:12:34,804 INFO  SDR100_STORE_SCU->dcmPACS (TCPServer-1-1) [org.dcm4cheri.net.FsmImpl] received A-ABORT
source=0 - service-user
reason=0 - reason-not-specified
2014-12-16 16:12:34,804 INFO  SDR100_STORE_SCU->dcmPACS (TCPServer-1-1) [org.dcm4cheri.net.FsmImpl] closing connection - Socket[addr=/192.168.9.240,port=1175,localport=11118]
2014-12-16 16:12:34,804 ERROR -> (TCPServer-1-1) [org.dcm4cheri.net.ActiveAssociationImpl] Received A-ABORT
source=0 - service-user
reason=0 - reason-not-specified
org.dcm4che.net.PDUException: Received A-ABORT
source=0 - service-user
reason=0 - reason-not-specified
at org.dcm4cheri.net.DimseReaderImpl.nextPDataTF(DimseReaderImpl.java:200)
at org.dcm4cheri.net.DimseReaderImpl.nextPDV(DimseReaderImpl.java:168)
at org.dcm4cheri.net.DimseReaderImpl.read(DimseReaderImpl.java:78)
at org.dcm4cheri.net.AssociationImpl.read(AssociationImpl.java:313)
at org.dcm4cheri.net.ActiveAssociationImpl.run(ActiveAssociationImpl.java:212)
at org.dcm4cheri.util.LF_ThreadPool.join(LF_ThreadPool.java:174)
at org.dcm4cheri.net.ActiveAssociationImpl.run(ActiveAssociationImpl.java:157)
at org.dcm4cheri.server.DcmHandlerImpl.handle(DcmHandlerImpl.java:249)
at org.dcm4cheri.server.ServerImpl.run(ServerImpl.java:288)
at org.dcm4cheri.util.LF_ThreadPool.join(LF_ThreadPool.java:174)
at org.dcm4cheri.util.LF_ThreadPool$1.run(LF_ThreadPool.java:221)
at java.lang.Thread.run(Thread.java:662)
2014-12-16 16:12:34,804 INFO  -> (TCPServer-1-1) [org.dcm4cheri.server.ServerImpl] finished - Socket[addr=/192.168.9.240,port=1175,localport=11118]
2014-12-16 16:12:48,984 INFO  -> (TCPServer-1-2) [org.dcm4cheri.server.ServerImpl] handle - Socket[addr=/192.168.9.240,port=1179,localport=11118]
2014-12-16 16:12:48,984 INFO  -> (TCPServer-1-2) [org.dcm4cheri.net.FsmImpl] Socket[addr=/192.168.9.240,port=1179,localport=11118]

Algie Rosario

unread,
Dec 16, 2014, 10:00:52 PM12/16/14
to dcm...@googlegroups.com
Thanks Gunter !

Shimadzu engineer adjust few settings in their  modality and it works fine. Thank you !

Cássio Vidal

unread,
Sep 13, 2018, 1:47:40 PM9/13/18
to dcm4che
HI, 

What configuration the engineer do?
Reply all
Reply to author
Forward
0 new messages