Lightstreamer getting issue on connection get grows

[rvkvino]

Hello,
This issue we have temporarily solved as restart adapter for twice per day. So today we restart the LS server on morning 6.30 A.M and after noon 2 P.M we closed and reopened the remote adapter so we didn't face this issue like connection close on 6 P.M to 7.P.M range. We think any memory leak on this whether LS server or remote adapter. Is there any way to clear the screen of adapter or memory.

[giuseppe.corti]

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 preferable to investigate the issue to determine where the leak resides and resolve it.

Regards,
Giuseppe

[rvkvino]

Hello,
i have created an adopter and connecting XXX number of different sites and streaming the data. on each time gap for example from the start time of the adopter on every 12 hours approximately it get stuck in peak hours. We need to know is there any memory limitations for each adopter which we build or any other limitation to be cleared on periodical basis.

If I restart my adapter 2 times per day then working fine without any issue.

And also I need to know how dynamically clear snapshot and recreate snapshot. It should be clear if data adapter held my memory issue or if it is any periodically need to clear the snapshot.

[giuseppe.corti]

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 Lightstreamer server releases the memory occupied by the snapshot for an Item in two cases:
1. no more client subscribe the involved Item;
2. the Data Adapter esplicitily call the clearSnapshot.

That said, have you tried to check the statistics of the memory occupied looking for the MonitorText logger lines?
If configured at the trace level it records the information every 2 seconds and can give a general overview of the progress of the memory.

Regards,
Giuseppe

[rvkvino]

Hello,
Now I have an issue like when the user close the tab that time session and connection automatically managed by lightstreamer. But when I check in my windows server currPorts in 8080 lot of connection in Time Wait and Close Wait status. Could you please let me know how the connection properly close in LS adapter or LS server. Because If connection in Close Wait or Time_Wait means lot of resources are using and getting memory leak and high CPU usages. So Please let me know the proper way to avoid this issue.

[giuseppe.corti]

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 tcp sockets are strongly dependent on any network intermediary like proxies or other devices in the middle between client and server.

Regards,
Giuseppe

[giuseppe.corti]

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 and therefore correctly all the tcp connections are handle by the same jvm running the Lightstreamer server.

The jvm running the Lightstreamer server listens on the tcp ports defined in your lightstreamer_conf.xml and then for each a client connection a dedicated tcp connection is established.
You can check the number of tcp connections established managed by the server in the log (MonitorText lines) or in the Monitoring Dashboard.

Regards,
Giuseppe