Page 3 of 3 FirstFirst 123
Results 21 to 29 of 29
  1. #21
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    973
    We cannot replicate the issue in these terms. I mean that if we
    • use a Server with version 6.0
    • configure a Proxy Adapter with version 1.7
    • include the
      <param name="init_remote">false</param>
      line in the Adapter configuration
    • use a remote adapter based on .NET Adapter library version 1.7,
      which used to work with Server version 5.1.2

    then it all works and the clients connect successfully.

    So, there must be something specific in your setup.
    In order to collect more information, the first step is to identify which is the executable that runs the Remote Server, so that we can properly configure its log.
    Can you manage to access the remote side and see how the Remote Server is launched?
    Is it an executable that was compiled on your side?

    If you prefer, you may rather produce a minimal subset of your deployment which triggers the problem, then pack it and attach it for us to check.

    By the way, please ensure that the <metadata_adapter_initialised_first> element is set to N, as we may have been unclear on this point.

  2. #22
    Senior Member
    Join Date
    Aug 2014
    Posts
    71
    how can i know the executable that runs the Remote Server?


    this is the code of launching the adapter

    Code:
            private void LaunchAdapter()
            {
                string host = "localhost";
                int reqrepPort = 7661;
                int notifPort = 7662;
    
    
                MetadataProviderServer ms = new MetadataProviderServer();
                ms.Adapter = new IntraDayAdapterUpdate();
                TcpClient mdreqrepSocket = new TcpClient(host, 6663);
                ms.RequestStream = mdreqrepSocket.GetStream();
                ms.ReplyStream = mdreqrepSocket.GetStream();
                ms.Start();
    
    
                DataProviderServer server = new DataProviderServer();
                server.Adapter = new IntraDayAdapterUpdate();
    
    
                TcpClient reqrepSocket = new TcpClient(host, reqrepPort);
                server.RequestStream = reqrepSocket.GetStream();
                server.ReplyStream = reqrepSocket.GetStream();
    
    
                TcpClient notif_Socket = new TcpClient(host, notifPort);
                server.NotifyStream = notif_Socket.GetStream();
    
    
                server.Start();
            }



    i check the
    <metadata_adapter_initialised_first> and it is N
    Last edited by engcoder; April 23rd, 2015 at 09:06 AM.

  3. #23
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    973
    Ok, sorry for the complication on terms.
    So, you wrote that source file; then you must have compiled it into some executable.
    This is the executable that, in our terms, runs the Remote Server; it links our .NET SDK library and hosts your Remote Adapter.

    This executable also links log4net and we have to configure it to show the log produced by the library.
    The configuration can be made in several ways; we suggest the following steps:
    1. Ensure that the line
      [assembly:log4net.Config.XmlConfigurator()]
      is inserted in the header of the previous source code;
      you can mimic this example.
      Obviously, if you should have to add the line, you must recompile.
    2. Add an "application configuration file" which contains the logback configuration.
      You can mimic this example.
      This file must be placed in the same directory as the Remote Server executable and named the same with a trailing ".config"; here is a reference documentation.
      Then rerun the Remote Server.


    Note that the log4net configuration in the "application configuration file" should be customized for your needs.
    With reference to the example provided above, we suggest:
    • keeping the current appender configuration, which produces the "DotNetServer.log" file;
    • setting all loggers to DEBUG level, but only for the time of this investigation.

  4. #24
    Senior Member
    Join Date
    Aug 2014
    Posts
    71
    can you see the following pic. it shows the LS open the port 8080 for connection and the 3 adapters with the full exception of the last adapter when try to connect to LS

    http://store1.up-00.com/2015-04/1429794838921.png


  5. #25
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    973
    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.

  6. #26
    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

  7. #27
    Senior Member
    Join Date
    Aug 2014
    Posts
    71
    hello,

    i try the new LS v 6.0 with Editing the Config. at another server and worked well!
    but at the local machine still gives the Exception of Client.Openconnection

    i have another question about the monitor of LS 6.0. I noticed that the monitor shows all values Zeros after some time despite there is free heap about 5 GB.
    why the monitor shows the values zeros in some times?

  8. #28
    Administrator
    Join Date
    Feb 2012
    Location
    Milano
    Posts
    539
    Hi engcoder,

    Just about the Monitor, if all figures are zero, including the number of sessions, then probably the Monitoring Dashboard has lost the connection with the server.
    Indeed, the Monitoring Dashboard is itself a session and then at a minimum you should see a number of sessions of 1.
    You should check, when the figures drop to zero, at the left-bottom of the page what was shown by the status widget.

    Regards,
    Giuseppe

  9. #29
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    973
    Can you take advantage of the new installation and dismiss the non-working one?
    If you are still interested in finding out what is wrong in your local installation, only the log on the Adapter can help us.

    The only possible guess, at this stage, is that, actually, the Remote Server in your local installation is not using the previous .NET Adapter library (1.7), but the new one (1.9).
    In this case, the "init_remote" setting as false causes the Remote Server to get a fatal error upon the first client request and to close the socket towards the Server and fail.
    Unfortunately, this does not give rise to the error you reported.
    But, perhaps, your launcher code ignores the error notification and this may cause the socket to remain open but unresponsive.
    The latter behavior could explain the timeout error reported in your Server log.

 

 

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 APIs
    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 11:50 AM.