Results 1 to 10 of 29

Hybrid View

  1. #1
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,091
    According to this report, the exception occurs on a Data Adapter which is, in turn, a client of some Lightstreamer Server.
    This is an architecture which may confuse us; so, before proceeding, please help us better clarify the scenario.
    Do you confirm that this Data Adapter (i.e. the one that starts at 04:08:13) opens a client session towards the same Server instance for which it acts as a Remote Adapter?
    In other words, do you confirm that there is only one LS Server instance involved?

    As we have found out so far, the root cause of your issue is in the Metadata Adapter not responding to the "notifyUser" requests from the Server.
    As shown by your "Remote Server" source code, the Metadata Adapter is run by the same process that runs one of your Data Adapters, namely the one that opens ports 7661 and 7662;
    hence, according to your adapters.xml file, the "Intraday2" Data Adapter.
    May you please specify, with respect to your screenshot, if the "Intraday2" Data Adapter is the one that starts at 04:07:56, at 04:08:02, or at 04:08:13 ?

    The next step is enhancing the log, so that we see the DEBUG log of the Metadata Adapter.
    Have you tried to configure the log as explained in my previous post, in particular for the executable that runs the Metadata Adapter?
    If yes, do you see any DotNetServer.log file? It should be created in the launch directory of the executable.

  2. #2
    Senior Member
    Join Date
    Aug 2014
    Posts
    71
    Do you confirm that this Data Adapter (i.e. the one that starts at 04:08:13) opens a client session towards the same Server instance for which it acts as a Remote Adapter?
    In other words, do you confirm that there is only one LS Server instance involved?
    Yes, only one

    May you please specify, with respect to your screenshot, if the "Intraday2" Data Adapter is the one that starts at 04:07:56, at 04:08:02, or at 04:08:13 ?
    it is that started at : 04:08:13

    The next step is enhancing the log, so that we see the DEBUG log of the Metadata Adapter.
    Have you tried to configure the log as explained in my previous post, in particular for the executable that runs the Metadata Adapter?
    If yes, do you see any DotNetServer.log file? It should be created in the launch directory of the executable.
    i will try to configure that and inform u

 

 

Similar Threads

  1. Replies: 7
    Last Post: April 20th, 2015, 09:10 AM
  2. Replies: 3
    Last Post: March 4th, 2011, 11:35 PM
  3. How to let Data and Metadata Adapters comunicate
    By CitiMan in forum Adapter SDKs
    Replies: 4
    Last Post: November 21st, 2008, 05:24 PM
  4. speed up initial loading
    By rd2008 in forum General
    Replies: 1
    Last Post: November 20th, 2008, 09:32 AM
  5. Accessing multiple adapters
    By Waddy in forum General
    Replies: 2
    Last Post: March 16th, 2007, 06:06 AM

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 04:25 PM.