-
December 16th, 2010, 09:48 AM
#1
Did you try to trace OpenConnection, SubscribeTable and CloseConnection callsas Dario suggests?
API issues unsubscription on it's own and connection gets lost.
Please can you clarify? Do you see unsubscription requests being sent to the server (can you attach a server log?) and after that the client closes the connection?
Please do not get confused by the unsubscription calls on the DataAdapter as those are not an evidence of the client sending an unsubscription request.
-
December 16th, 2010, 12:07 PM
#2
Hi,
I'm sorry, I forgot to mention that there is a known bug in the current library that, if the stream-sense is active (see http://lightstreamer.com/docs/client...eamSense1.html ) can lead to refused subscriptions (this only happens if subscriptions are performed soon after the openConnection method exits due to a race condition).
We may provide you with a fixed library if you can't wait for the official release expected in Q1 2011. If that's the case please write to support@lightstreamer.com.
-
December 16th, 2010, 08:41 PM
#3
Loss of connection
Hi Mone,
We are attempting streaming connection with lightstreamer :
connectionInfo.Polling = false;
connectionInfo.User = Guid.NewGuid().ToString();
We dont set the stream sense defaulting it to "true"
We did more debugging and found that, We made create session request "17:37:31", made binding request "17:37:36". Server waited for 5 second and issued session close / destory. It seems for some reason the client api didnt make binding request for long 5 second resulting into session closure. This is resulting in subscription exception (SubscrException) in the application code.
We are attempting to fix this by handling this connection and attempting a reconnect? Is this right thing to do or you think this is the issue you were refereing in your previous post and getting latest version of silverlight client api will fix this?
-
December 17th, 2010, 09:30 AM
#4
Hi,
I suggest going on this way:- disable the stream sense and try to reproduce the issue.
- (with stream sense enabled) place a sleep of a couple of seconds between the openConnection and the subscribe call and try to reproduce the issue
if none of the above reproduced the issue, then you're probably experiencing our bug, otherwise the issue should be somewhere else.
In any case, if possible, attach here the server log showing one of the sessions that had the issue.
Similar Threads
-
By ned_b in forum Client SDKs
Replies: 4
Last Post: August 24th, 2011, 10:31 AM
-
By emiliob in forum Client SDKs
Replies: 7
Last Post: June 21st, 2010, 02:59 PM
-
By gjoseph in forum Client SDKs
Replies: 1
Last Post: November 13th, 2009, 11:14 AM
-
By latha in forum Adapter SDKs
Replies: 9
Last Post: June 3rd, 2009, 09:56 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 10:51 PM.
Bookmarks