Utils.WaitForComplete in Dicom Workist service

Options

View

Last

Unread

Previous Topic Next Topic

This topic and its replies were posted before the current version of LEADTOOLS was released and may no longer be applicable.

#1 Posted : Monday, October 1, 2018 2:07:00 PM(UTC)

Dan Howard

Groups: Registered
Posts: 8

Thanks: 1 times

In the sample code for the listening service we have method to block a thread and listen on a port.

Sometimes we have the issue where if the service is restarted we'll get a "port is in use" message.

I'm guessing it's because the service stopping event is not interrupting that blocking thread.

You can see this in CSDicomHighlevelMWLScuDemo_x86_2010 project.

Any ideas on how to address that issue?


	Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads Wanna join the discussion? Login to your LEADTOOLS Support account or Register a new forum account.

#2 Posted : Tuesday, October 9, 2018 1:25:22 PM(UTC)

Christopher Thompson

Groups: Registered, Tech Support, Administrators
Posts: 89

Was thanked: 4 time(s) in 4 post(s)

Typically, due to the way the the PACS communication works in regards to the AE Title, Port, and IP address,
the use of multi-threading or connections can cause a number of connection issues.

The issue that you are describing is one of these.
There is not a known work around regarding this.

Depending on how you are setting the connection to the PACS server,
you could try beginning with checks to see if the port is in use,
followed by an attempt to close any threads that you blocked previously.

Chris Thompson
Developer Support Engineer
LEAD Technologies, Inc.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.