LDicomNet callbacks are not triggered

hi,

we have a SCP server application which works fine (our SCP
is a specialization of LDicomNet class). Now, when we tried making use of the
same class in a windows service application, no callbacks are triggered (we hav
our overrides). All the pre conditions for Listen() are met and Listen()
returns DICOM_SUCCESS. A call to IsActivated() returns true after the listen(). Are there any issues for LDicomNet being used in a service?
The flow of our service –

On start{
Start timer 05 secs
}

On timer’s elapse{
Init LEAD support
Startup
Scp-> listen
/// call to scp->IsActivated() returns true here
}

OnStop{
/// call to scp->IsActivated() returns true here too
/// Clean up
}

Any help appreciated.
Thanks.

What callbacks are you overriding and do not work?  I understand
that all the callbacks are fired in the Windows application.  Is that correct?

the overridden callbacks -
    OnAccept
    OnReceiveAssociateRequest
    OnReceiveCStoreRequest
    OnReceiveReleaseRequest
    OnClose

Listen returns DICOM_SUCCESS
IsActivated returns true
On SCU trying to connect, the OnAccept is not fired.

its true that all the callbcaks are fired in the application, but NOT in the service (i use the same SCP specialization).

Please check the value of IsConnected right after the client connects
to the server.  I am working on a similar issue in another thread and in this one, IsConnected is False after the connection is made.

I do not have any information about how the callbacks are internally
implemented.  Can you please post a small test projects (not your
full project) for an SCP and SCU that show the problem?  I know
this might not be easy to do, but if there is a problem in the toolkit, then this is the only way to track it down.

Hello,

Was a solution ever provided to the issue presented at the start of this post? I am experiencing the same issue. My SCP application works fine when hosted in a Windows Forms application. However, when I move the code into a Windows Service the events/callbacks (i.e. OnAccept) are never triggered.

Thank you in advance,

Andrew

Hello,

We are also facing the same scenario.
Is this resolved? Please respond.

Thanks
Saumin

Hello!

Is this resolved yet? we are also facing the same problem. Please respond.

Thanks,
Saumin

Hello All,

I was able to duplicate this issue and have submitted this to our engineers. I will post again when I hear back from them.

We have resolved the issue with receiving events inside a Windows Service.

Internally the LEADTOOLS DICOM DLL uses Window's Messages to communicate with Window's Sockets. So you must have a Message Pump so the messages can get processed. In your worker thread simply add a message pump after calling Listen.

The attached demo simply shows one method of implementing this. I'll give a brief walkthrough: We spawn a worker thread in the OnStart event. In the worker thread we create an instance of our Scp Class and call Listen. Following this call we created a function called WaitForComplete. This function has a message pump in it and also checks to see if want the loop to exit. In the Windows Service OnStop event we signal for the WaitForComplete function to exit so the child thread can clean up and exit.

Again this is one implementation. Feel free to develop your own just keep in mind that a message pump must exist in the thread the Listen is in.

The code also creates an EventLog so you can see when the OnAccept function is called.

I find exactly the same behaviour when using the Multimedia Library to convert from .avi to .asf in a Windows Service. As soon as I set the .TargetFile property, it just goes off and does absolutely nothing. (Never executes the next line of code nor does it throw an exception)

Adnan,

I'm trying to convert from .avi to .asf, using ltmmConvert, in a Windows Service (VB.Net) but, as soon as I set the .TargetFile property, it just goes off
and does absolutely nothing. (Never executes the next line of code nor does it throw an exception).

It works perfectly in a Windows Forms application, but no luck in a Windows Service.

I'm experiencing something similar when using the Multimedia Library to convert from AVI to ASF with the convert class inside a Windows Service.
Is there any way you can show me how to implement a similar message pump in VB.Net?

This is really not anything that is LEAD specific, however, I will help you out here.

Attached is code in C# and VB.NET. It is the basic concept of having a message pump in your service. As you'll see there is no LEADTOOLS code involved.

I have attached the same project using Getmessage instead of PeakMessage for the message pump. This is a much better solution for performance and keeps the CPU utilization down.

Also, here is a project to go with the C# version.