Search:

Type: Posts; User: giuseppe.corti

Search: Search took 0.03 seconds.

  1. Hi Vinoth Kumar, But please let me stress out...

    Hi Vinoth Kumar,

    But please let me stress out that this is not an issue, it is normal that your server has an established connection for each connected client.
    If you want to handle 50K...
  2. Hi Vinoth Kumar, As you can see from the...

    Hi Vinoth Kumar,

    As you can see from the process id column, which always contains the same value, the java.exe process is just only one.
    The situation is correct, as you have to expect a...
  3. Hi Vinoth Kumar, No, I confirm that no...

    Hi Vinoth Kumar,

    No, I confirm that no java.exe have to start for each new client connection.
    The picture you attached is quite small, but it seems however that the process id is always the same...
  4. Hi Vinoth Kumar, You could call explicitly the...

    Hi Vinoth Kumar,

    You could call explicitly the disconnect() method but I don't know if in your client you can properly identify how trigger the call.
    In any case TIME_WAIT and CLOSE_WAIT on the...
  5. Are there in your adapters code some data...

    Are there in your adapters code some data structure as a queue or a map? Indeed these are potential candidates to generate memory leaks since they can grow indefinitely if not properly managed.
    The...
  6. Hi Vinoth Kumar, The only way to influence the...

    Hi Vinoth Kumar,

    The only way to influence the memory held by the server is through the 'clear snapshot' request that your Data Adapter can issue for the subscribed Items.
    But it would be...
  7. I'm really puzzled that you didn't find any...

    I'm really puzzled that you didn't find any evidence of adapter disconnections.
    Please consider that the disconnection may have happened a long time (several hours) before than the error messages...
  8. So this means that the Metadata Adapter was...

    So this means that the Metadata Adapter was already down but didn't reconnect or reconnect with some delays.

    You should look in the log file for the exact moment where the Metadata Adapters go...
  9. I can confirm that errors you reported us are due...

    I can confirm that errors you reported us are due to a connection interruption between the Lightstreamer server and your remote Metadata Adapter.
    Maybe the implementation of notifyUser method in the...
Results 1 to 9 of 9
All times are GMT +1. The time now is 09:26 AM.