The connection status shows CONNECTING

VictorYew

Hi there,

I am applying 5.1.1 Colosseo on Flex Mobile Project. I managed to set up the connection and subscribe to the table in the emulator and the status is showing 'STREAMING'. BUT, the status turns into 'CONNECTING' when it tries to connect for the third time. The following is my status:

//first time
DISCONNECTED => CONNECTING
CONNECTING => STREAMING

//second time
DISCONNECTED => CONNECTING
CONNECTING => STREAMING

//third time
DISCONNECTED => CONNECTING
........

Please help.

Giuseppe Corti

Hi Victor,

We would need some more details to go deeper into the issue.
Can you define the scenario of your test? The three attempts you mention are performed one after another, maybe against a connection drop, or you start three parallel connections running simultaneously to the same server?

However, if it is possible for you, please attach a snippet of Lightstreamer server log with the isolated case of the issue.

VictorYew

Giuseppe Corti Hi Victor,

We would need some more details to go deeper into the issue.
Can you define the scenario of your test? The three attempts you mention are performed one after another, maybe against a connection drop, or you start three parallel connections running simultaneously to the same server?

Ok. Here's the scenario. I build this application where it has a muti-tab panel in flex. The first panel connects to the lightstreamer server and manage to subscribe to the table. Then, I navigate to the second panel which loads an empty page and I navigate back to the first panel which again connects to the lightstreamer server without error. THEN, I repeat the process and this time it fails to connect to the server with the connection status showing 'CONNECTING'. It stays the same for every attempt afterwards.

Does that mean I have to close the connection to the lightstreamer server every time I leave the first panel before I make a new connection in the second attempt?

(Please note that the test is performed under stable internet connection and I can reproduce the error every time I repeat the test.)

Giuseppe Corti

Hi Victor,

You've probably reached the limit of connection pool (to the same host) that the environment of your client allow.
As a general rule, if in the second attempt you create a new object, then yes, you have to close the connection on the previous one in order to avoid to burst the connection pool.
Alternatively, you can arrange your code to reuse the same object each time.

VictorYew

Hmm..I see. Thank you for the information, Corti.