DICOM @ OFFIS

Discussion Forum for OFFIS DICOM Tools - For registration, send email with desired user name to the OFFIS DICOM team
It is currently Sun, 2017-12-17, 22:26

All times are UTC + 1 hour




Post new topic Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Mon, 2017-08-28, 11:20 
Offline

Joined: Fri, 2017-06-23, 09:50
Posts: 8
We want to send some big video files to our DCMTK server. However it fails for video bigger than 2 GB.
We got following console output:
Code:

C:\Users\Xion\Downloads\dcmtk-3.6.2-win64-dynamic>start .\bin\wlmscpfs.exe -ll trace -dfp .\share\dcmtk\wlistdb 104" -csk

C:\Users\Xion\Downloads\dcmtk-3.6.2-win64-dynamic>.\bin\storescp.exe --log-level trace -xf ".\etc\dcmtk\storescp.cfg" "Default" 105"
D: $dcmtk: storescp v3.6.2 2017-07-14 $
D:
T: Timeout while waiting for incoming network data
T: Timeout while waiting for incoming network data
T: Timeout while waiting for incoming network data
T: Timeout while waiting for incoming network data
T: Timeout while waiting for incoming network data
T: Timeout while waiting for incoming network data
T: Timeout while waiting for incoming network data
T: Receiving data via select()
T: checking whether environment variable TCP_BUFFER_LENGTH is set
T:   environment variable TCP_BUFFER_LENGTH not set, using the system defaults
T: checking whether environment variable TCP_NODELAY is set
T:   environment variable TCP_NODELAY not set, using the default value (0)
D: setting network send timeout to 60 seconds
D: setting network receive timeout to 60 seconds
T: DUL  FSM Table: State: 1 Event: 4
T: DUL  Event:  Transport connection indication
T: DUL  Action: AE 5 Transport Connect Response
T: Read PDU HEAD TCP: 01 00 00 00 00 e9
T: Read PDU HEAD TCP: type: 01, length: 233 (e9)
T: DUL  FSM Table: State: 2 Event: 5
T: DUL  Event:  A-ASSOCIATE-RQ PDU (on transport)
T: DUL  Action: AE 6 Examine Associate Request
D: PDU Type: Associate Request, PDU Length: 233 + 6 bytes PDU header
D:   01  00  00  00  00  e9  00  01  00  00  53  54  4f  52  45  53
D:   43  50  20  20  20  20  20  20  20  20  44  69  56  41  53  20
D:   20  20  20  20  20  20  20  20  20  20  00  00  00  00  00  00
D:   00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
D:   00  00  00  00  00  00  00  00  00  00  10  00  00  15  31  2e
D:   32  2e  38  34  30  2e  31  30  30  30  38  2e  33  2e  31  2e
D:   31  2e  31  20  00  00  43  01  00  00  00  30  00  00  20  31
D:   2e  32  2e  38  34  30  2e  31  30  30  30  38  2e  35  2e  31
D:   2e  34  2e  31  2e  31  2e  37  37  2e  31  2e  34  2e  31  40
D:   00  00  17  31  2e  32  2e  38  34  30  2e  31  30  30  30  38
D:   2e  31  2e  32  2e  34  2e  31  30  33  50  00  00  41  51  00
D:   00  04  00  00  40  00  52  00  00  21  31  2e  32  2e  38  32
D:   36  2e  30  2e  31  2e  33  36  38  30  30  34  33  2e  31  2e
D:   31  2e  38  2e  36  34  2e  32  37  2e  30  55  00  00  10  44
D:   69  63  6f  6d  4f  62  6a  65  63  74  73  2e  43  4f  4d
D: Parsing an A-ASSOCIATE PDU
T: PDU type: 1 (A-ASSOCIATE RQ), PDU Length: 233
T: DICOM Protocol: 1
T: Called AP Title:  STORESCP
T: Calling AP Title: MyApp
T: Parsing remaining 165 bytes of A-ASSOCIATE PDU
T: Next item type: 10
T: Subitem parse: Type 10, Length 0021, Content: 1.2.840.10008.3.1.1.1
T: Successfully parsed Application Context
T: Parsing remaining 140 bytes of A-ASSOCIATE PDU
T: Next item type: 20
T: Parsing Presentation Context: (20), Length: 67
T: Presentation Context ID: 01
T: Parsing remaining 63 bytes of Presentation Context
T: Next item type: 30
T: Subitem parse: Type 30, Length 0032, Content: 1.2.840.10008.5.1.4.1.1.77.1.4.1
T: Successfully parsed Abstract Syntax
T: Parsing remaining 27 bytes of Presentation Context
T: Next item type: 40
T: Subitem parse: Type 40, Length 0023, Content: 1.2.840.10008.1.2.4.103
T: Successfully parsed Transfer Syntax
T: Successfully parsed Presentation Context
T: Parsing remaining 69 bytes of A-ASSOCIATE PDU
T: Next item type: 50
T: Parsing user info field (50), Length: 65
T: Parsing remaining 65 bytes of User Information
T: Next item type: 51
T: Maximum PDU Length: 16384
T: Successfully parsed Maximum PDU Length
T: Parsing remaining 57 bytes of User Information
T: Next item type: 52
T: Subitem parse: Type 52, Length 0033, Content: 1.2.826.0.1.3680043.1.1.8.64.27.0
T: Parsing remaining 20 bytes of User Information
T: Next item type: 55
T: Subitem parse: Type 55, Length 0016, Content: DicomObjects.COM
T: Successfully parsed User Information
I: Association Received
D: Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.2
D: Our Implementation Version Name:   OFFIS_DCMTK_362
D: Their Implementation Class UID:    1.2.826.0.1.3680043.1.1.8.64.27.0
D: Their Implementation Version Name: DicomObjects.COM
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    MyApp
D: Called Application Name:     STORESCP
D: Responding Application Name:
D: Our Max PDU Receive Size:    16384
D: Their Max PDU Receive Size:  16384
D: Presentation Contexts:
D:   Context ID:        1 (Proposed)
D:     Abstract Syntax: =VideoPhotographicImageStorage
D:     Proposed SCP/SCU Role: Default
D:     Proposed Transfer Syntax(es):
D:       =MPEG4BDcompatibleHighProfile/Level4.1
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation:  none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response:  none
D: ======================= END A-ASSOCIATE-RQ ======================
T: DUL  FSM Table: State: 3 Event: 6
T: DUL  Event:  A-ASSOCIATE resp prim (accept)
T: DUL  Action: AE 7 Send Associate AC
D: Constructing Associate AC PDU
I: Association Acknowledged (Max Send PDV: 16372)
D: ====================== BEGIN A-ASSOCIATE-AC =====================
D: Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.2
D: Our Implementation Version Name:   OFFIS_DCMTK_362
D: Their Implementation Class UID:    1.2.826.0.1.3680043.1.1.8.64.27.0
D: Their Implementation Version Name: DicomObjects.COM
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    MyApp
D: Called Application Name:     STORESCP
D: Responding Application Name: STORESCP
D: Our Max PDU Receive Size:    16384
D: Their Max PDU Receive Size:  16384
D: Presentation Contexts:
D:   Context ID:        1 (Accepted)
D:     Abstract Syntax: =VideoPhotographicImageStorage
D:     Proposed SCP/SCU Role: Default
D:     Accepted SCP/SCU Role: Default
D:     Accepted Transfer Syntax: =MPEG4BDcompatibleHighProfile/Level4.1
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation:  none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response:  none
D: ======================= END A-ASSOCIATE-AC ======================
T: DIMSE receiveCommand
T: DUL  FSM Table: State: 6 Event: 16
T: DUL  Event:  Transport connection closed
T: DUL  Action: AA 4 Indicate AP Abort
I: Association Aborted


What can we do about this? We use the latest dcmtk-3.6.2-win64 version.


Top
 Profile  
 
PostPosted: Thu, 2017-09-14, 10:41 
Offline
DCMTK Developer

Joined: Tue, 2011-05-03, 14:38
Posts: 1882
Location: Oldenburg, Germany
Did you already try to start storescp with option --bit-preserving (+B)? This will tell storescp to receive the DICOM dataset directly to file and not to main memory (before writing it to a file).

Also, are you sure that the abort is not caused by the SCU (see message "Transport connection closed" at the end of the log output)?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: Bing [Bot] and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group