Results 1 to 10 of 10

Hybrid View

  1. #1
    Power Member
    Join Date
    Sep 2013
    Location
    Coimbatore
    Posts
    121
    Thanks for your reply.
    This is working for me now. When I refresh the page it didn't get terminate the currently active session. But my goal is I have to terminate if any other session opened with my credential.(User Name is unique.) If anyone opened my application by using my credential in that time If I open my browser means my session only should be active and their session should get inactive and force their page to logout. Now I think It getting terminate the existing session.(I have checked in 2 browsers by using the same credential ). But I didn't get any response from Ls while getting terminate the session. If I get the session lost message means I could force the logout the page from the client side. Is it possible getting response while terminate the session.
    I have tried in this way
    lsClient.addListener({
    onServerError: function(errorCode, errorMessage) {
    //here you can consume the error
    console.log("Connection Error: " + errorCode, errorMessage);
    }
    });

    onSubscriptionError: function(errorCode, errorMessage) {
    //here you can consume the error
    console.log(errorMessage);
    },
    onCommandSecondLevelSubscriptionError:function(err orCode,errorMessage,relatedkey) {
    //this one can only be fired in case a two-level subscription is created
    //here you can consume the error
    }
    Last edited by rvkvino; November 6th, 2017 at 12:48 PM.

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,091
    If you refresh the page, the old page should be destroyed before it can get the session close notification;
    but if you open a new page on a different browser, the previous page is supposed to receive an invocation in onServerError, notifying error code 35.
    It is strange that you didn't see anything.

    We have to trace what happens.
    Please reproduce the case on a dedicated Server instance, by opening only the two involved pages on two different browsers.
    To keep the logs short, you should also prevent the pages from performing subscriptions, which are not relevant in this case.
    As a first step, show us the Server log, taken after setting LightstreamerLogger.push at DEBUG level.

 

 

Similar Threads

  1. Light streamer for Login user
    By in forum General
    Replies: 0
    Last Post: September 24th, 2022, 12:52 PM
  2. Light streamer user session maintenance
    By rvkvino in forum General
    Replies: 1
    Last Post: February 24th, 2017, 10:06 AM
  3. Light streamer for Login user
    By rvkvino in forum General
    Replies: 3
    Last Post: September 25th, 2013, 09:20 AM
  4. connect Light streamer and j2EE web application
    By pradeepgamage in forum Adapter SDKs
    Replies: 7
    Last Post: May 17th, 2012, 09:21 AM
  5. Replies: 5
    Last Post: September 8th, 2009, 03:07 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 08:46 PM.