I'm working on source code downloaded on 13/12/2011,

Windows 7 64 Ultimate edition with a SQL Server 2008 R2 - IIS 7.5

Internal net.

When i open Webviewer to view a study, the window in the browser opens quickly, but the image shows up after a time between 3 and 60 seconds.

Any command or mouse feedback on the images or interface shows the same lag.

In the debug window of the Silverlight application i can see many text lines like 'Received message set out of order (received:16,expected:3)' (the numbers to show you message number received many greater than number expected).

If i compare time of message of mouse events sent from Silverlight to server, i see the receive time is 5 to 60 seconds later the invoice.

Obviously the Web viewer is unusable.

What's happen?

How can i fix this?

Thanks in advance

What version of the code are you using? I know we've seen this a few times in the past, but I thought we'd resolved the issues in more recent versions of the code. I don't really recall what the source of the issue was originally, although I do seem to remember the problem was sporadic. In any case, you might want to use either a recent version of the Trunk, or the code in the McCoy branch in Mercurial.

Steve

I downloaded a fresh copy of the code.

The behaviour is the same as above.

But, when i change, in project Clearcavas.Web.Service, file ApplicationService.cs, function GetPendingEvent, the line:

EventSet = application.GetPendingOutboundEvent(Math.Max(0, request.MaxWaitTime))

with:

EventSet = application.GetPendingOutboundEvent(0),

the browser is much more responsive.

Maybe there are settings in IIS are responsible for this behavior?

 

Antonio,

So, with the latest code, we do polling from the client to the server to check for messages. When we moved to using IIS & using an HTTP binding, we no longer could send events directly from the server to the client, so instead we had to implement a polling mechanism. There's a MaxWaitTime parameter passed that tells how long the server should wait for a message to be ready for the client before the call just returns. The client tells how long it wants the server to wait before returning if there's no message to send back to the client.

I'd surmise the source of the problem is that the ordering of the messages being sent to the client is causing problems where the client has to process the messages before it can send new requests to the server, and somehow the delay is causing the messages to be processed slower. The core of the problem is probably in those out of order messages that are being reported in the client. I'm not really sure what the issue is, but its something about ordering of messages with http & IIS.

Steve