Memory Leak - LightstreamerClient.disconnect() does not stop threads [Java]

[gianluca.finocchiaro]

Hi Klaus,

thank you very much for your feedback!

At first sight your project would seem ok, but when cloned and launched from my machine I can't see any real time update coming from the remote server. It may be a symptom that something has gone wrong in the subscription phase, so I ask you to check it with your service provider and then get back to us to go on with our investigation.

Regards,
Gianluca

[Klaus Groenbaek]

Hi Gianluca

The service provider didn't document which mode I should use when subscribing to their Orders stream, I found a forum entry that said I could use DISTINCT, or RAW, and unlucky as I was I picked DISTINCT.
Strangely enough DISTINCT worked about 80% of the time with LS5 and LS6-b2, but not the final LS6. After I got a running example from the service provider I noticed that they used RAW, and after I made that adjustment it worked fine.
I'm a little puzzled about the 20% periodic failure rate, but I'm thinking it's related to some implementation detail in the service provider, and they probably never tested it or planed it to work with DISTINCT mode.

Thanks again, for taking time to look at this.

/Klaus

[giuseppe.corti]

Hi Klaus,

I confirm that you should always be aware of which mode to use in your subscriptions on the client.

Indeed, at the server side, the Metadata Adapter should always define the subscription methods permitted for each Item through a proper implementation of the isModeAllowed method.
If this is not done, or are admitted for the same Item two conflicting modes, we could have unpredictable behavior.

For example if a client subscribe an Item in MERGE mode and a subsequent client requesting the same Item in DISTINCT mode, this will be eventually refused by Lightstreamer server.
But, if we invert the temporal order of the two clients, only the DISTINCT subscriptions will work.

Regards,
Giuseppe