We encounter a strange problem when using SendCStoreRequest, based on the moveimages examples. In a test situation we can send 5 or 6 images per second. At one customer we have a long delay between de "release request" and the "relase reponse". Typically the time between them is 0 hundredth's of a second. But now it ranges between 5s and 2 minutes! The firewall is off, the receiver indicates that it sends de response directy. 2 log lines.--14:42:36:41 C-STORE-REQUEST: Sending release request... Not Done yet--14:44:14:64 C-STORE-REQUEST: Receiving release response DoneNormal:--15:12:52:56 C-STORE-REQUEST: Sending release request... Not Done yet--15:12:52:56 C-STORE-REQUEST: Receiving release response Done

We have looked at the communication with Wireshark and the response seems to come in after that extra time. Are there any other places where we can look for a solution?

A secundary problem here is, that when using an example WaitForComplete() with a WaitOne for TimeSpan 1 tick, the CPU rockets to 100%, we have set is at 10000 ticks for now, any comments on that?

There isn't enough information here to draw any conclusions. If I understand the issue here, you are saying the server is taking around two minutes to send a release response back to the client. There could be many reasons for this, and it isn't necessarily indicative of a problem.

Have you checked the server log to see what it was doing in that time period? Perhaps it is busy with other requests and thus takes a long time to clean up all of it's resources.

Does the server support MPPS and is it confirming all operations completed perhaps?

What server is being used here? That information has also been omitted. Are you testing against a LEADTOOLS server or another 3rd party server? If it is a LEADTOOLS server, which server are you testing again? What version is it?

It would seem likely that the server is receiving the release request. If not, you might expect the server to timeout the connection and abort it. This would typically happen in under two minutes (usually 30-60 seconds). If that were to happen, you would get an abort response.

Thanks for the quick reply, more testing with our own local receiver shows a normal response time. At this moment it looks as if the remote server just takes a long time responding to our "release request". It apparently does some work after the release request before sendig the response and that takes some time.

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.