Hi

Sorry I did not found the Bugs reporting forum....

The use case is the following (Inactivity Time out):
RECEIVE ASSOCIATE-RQ (
PRESENTATION-CONTEXT-ITEMS
("Verification SOP Class", "Explicit VR Little Endian")

)

SEND ASSOCIATE-AC (
PRESENTATION-CONTEXT-ITEMS
("Verification SOP Class", 0, "Explicit VR Little Endian" )
)

RECEIVE C-ECHO-RQ

DELAY 60

RECEIVE ABORT-RQ (
SOURCE 0
REASON 0
)

From the client point of view I send the abort RQ and just after I close the socket.

It seems that a decoupling is missing in Dvtk between Network and script validation. In my scenario dvt prints an error "TCP/IP error socket was closed ...". If I just wait 2s between Abort Request and Close Socket , it makes Dvtk happy :)


Thanks in advance for your feed back

Seb

PS: my version is Dvtk 2.1.4

Hi,
For logging bugs on DVTk, please register yourself first on DVTk.org.
It'll not take more then 5 minutes of ur time. In return you will get lot(Latest version of DICOM tools).
After registering you will see the link "Log Problems/Ideas", you can log the bug using this link.

Pl register & log the bug.

Regards,
Piyush