Hi,
we are having strange log in our system. Please check the screen shot for detail. The system is working fine but still the log is suspicious. Thanks.
Regards
SH
Printable View
Hi,
we are having strange log in our system. Please check the screen shot for detail. The system is working fine but still the log is suspicious. Thanks.
Regards
SH
Hi shabbirh,
we can not find the screen shot you're talking about, please you may re-post it?
Thank you.
Here is the screenshot
Attachment 139
Hi,
Looks like something is blocking the websocket connection.
Your application still works because when the library detects that it can't use the websocket connection it falls back to http streaming.
Please open this demo, then move your mouse over the S on the top-left of the page. Does it say "over WebSocket" or "over HTTP"? This will tell us if yours is a client or server side issue.
Is there a load balancer and/or reverse proxy in front of your server?
Please check this file, is your environment correctly configured for firefox running over websockets?
Yes, we are using a load balancer/reverse proxy in front of our server. I guess the websocket connection is interrupted due to the load balancer. Is there any solution to use web socket connection in our load balancer ? What is the performance issues between HTTP streaming and Websocket? Thanks.
Quote:
I guess the websocket connection is interrupted due to the load balancer.
You were able to connect over WebSocket to our demo server?
It depends on the balancer you're using; you should check its documentation and/or get in touch with the balancer vendorQuote:
Is there any solution to use web socket connection in our load balancer ?
As long as we're talking about one way traffic (server->client) server performances are quite the same, the only difference is that HTTP streaming needs to be refreshed from time to time (this may add some load but is usually neglectable); client performances may vary.Quote:
What is the performance issues between HTTP streaming and Websocket?
On the other hand subscription/unsubscription/messages during a session over websocket are sent through the open websocket while during a http streaming session a new http request needs to be sent to the server (and thus possibly a new socket may be needed)
HTH