Lightstreamer unknown error using C# client

ynor

Hello,

Can someone help me identify this error:
http://content.invisioncic.com/h238858/monthly_2020_08/image.png.18aeec3d105bc29958e2557a91fbec32.png

Dario Crivelli

Hello,

The client receives no answer to a simple https request.
This can only be an issue related with the local environment.
Perhaps something fails in the TLS handshake.
Do you confirm that, after 12:34:42, other connection attempts are made, all with the same outcome?

I suppose that you have no control on the Server.
What client SDK version are you using?
Please try to take a client side packet capture, to see if something comes back fron the Server.

ynor

Hello,

I am using .NET Lightstreamer.DotNetStandard.Client (5.0.5).

I was able to change it via ForcedTransport but I am still getting this error:

Property serverSocketName changed:
Property clientIp changed:
Property serverInstanceAddress changed:
https://push.cityindex.com/
Property realMaxBandwidth changed:
2020-08-25 10:15:13.5568|DEBUG|lightstreamer.stream|IsOffline check now ...
2020-08-25 10:15:13.6092|DEBUG|lightstreamer.stream| ... online, go!
2020-08-25 10:15:13.6092|DEBUG|lightstreamer.protocol|Create Request: https://push.cityindex.com/
2020-08-25 10:15:13.6092|INFO|lightstreamer.utils|Cookies to be inserted for https://push.cityindex.com/lightstreamer/create_session.txt?LS_protocol=TLCP-2.1.0: <none>
2020-08-25 10:15:13.6092|DEBUG|lightstreamer.stream|cs ---- address: https://push.cityindex.com/lightstreamer/create_session.txt?LS_protocol=TLCP-2.1.0, 213.86.152.51
2020-08-25 10:15:13.6168|DEBUG|lightstreamer.stream|HTTP transport connection establishing (oid=4): https://push.cityindex.com:443
/lightstreamer/create_session.txt?LS_protocol=TLCP-2.1.0
LS_polling=true&LS_cause=new.network.error&LS_polling_millis=0&LS_idle_millis=0&LS_cid=jqWtj1twChtfDxikwp1ltvcB4BJ9Ji kOj2CQf&LS_adapter_set=STREAMINGALL&LS_user=<removed>&LS_password=<removed>&LS_old_session=&

2020-08-25 10:15:13.6168|DEBUG|lightstreamer.stream| - target: 213.86.152.51:443 - False(com.lightstreamer.client.transport.providers.netty.NettyFullAddress).
2020-08-25 10:15:13.6168|DEBUG|lightstreamer.session|sessionStatusChanged 10, 10
2020-08-25 10:15:13.6168|DEBUG|lightstreamer.netty.pool|HTTP channel created [0f90c596, com.lightstreamer.client.transport.providers.netty.NettyFullAddress]: False
>>>>>>>>>>>>>>>>>> CONNECTING -
2020-08-25 10:15:13.6168|DEBUG|lightstreamer.session|Session state change (4): OFF -> CREATING
2020-08-25 10:15:13.6168|DEBUG|lightstreamer.session| phasing : 1 - 1
2020-08-25 10:15:13.6168|DEBUG|lightstreamer.session|Status timeout in 4000 [currentConnectTimeout] due to
2020-08-25 10:15:13.7393|DEBUG|lightstreamer.netty.pool|HTTP channel active [0f90c596]
2020-08-25 10:15:13.7393|DEBUG|lightstreamer.stream| - acquired! 0f90c596
2020-08-25 10:15:13.7393|DEBUG|lightstreamer.stream|Go with the request True
2020-08-25 10:15:13.7393|DEBUG|lightstreamer.stream|Send Request Task status = RanToCompletion
2020-08-25 10:15:13.8611|ERROR|lightstreamer.stream|HTTP transport error [0f90c596]
2020-08-25 10:15:13.8611|ERROR|lightstreamer.stream|HTTP transport error [0f90c596]
2020-08-25 10:15:13.8744|DEBUG|lightstreamer.netty.pool|Socket error.
2020-08-25 10:15:13.8744|DEBUG|lightstreamer.stream|Channel closed [0f90c596]
2020-08-25 10:15:13.8744|DEBUG|lightstreamer.netty.pool|HTTP channel inactive [0f90c596]
2020-08-25 10:15:13.8744|DEBUG|lightstreamer.netty.pool| ... False - False
2020-08-25 10:15:13.8744|DEBUG|lightstreamer.netty.pool|Socket Closed.
2020-08-25 10:15:13.8744|ERROR|lightstreamer.session|Error event while CREATING reason: network.error tryRecovery=True timeLeft=15000 closedOnServer=False unableToOpen=False wsError=False
2020-08-25 10:15:13.8744|ERROR|lightstreamer.session|Error event while CREATING reason: network.error tryRecovery=True timeLeft=15000 closedOnServer=False unableToOpen=False wsError=False
2020-08-25 10:15:13.8833|DEBUG|lightstreamer.session|Error event for network.error while CREATING
2020-08-25 10:15:13.8833|DEBUG|lightstreamer.session|Start new session. Cause: socket error in 0
2020-08-25 10:15:13.8833|INFO|lightstreamer.session|Closing session network.error
2020-08-25 10:15:13.8833|DEBUG|lightstreamer.subscribe|SubscriptionManager sessionAlive set to false.
2020-08-25 10:15:13.8833|INFO|lightstreamer.subscribe|Reset message handler
2020-08-25 10:15:13.8833|DEBUG|lightstreamer.subscribe|Aborting pending messages
2020-08-25 10:15:13.8833|DEBUG|lightstreamer.session|SessionManager state change: POLLING_HTTP -> POLLING_HTTP
2020-08-25 10:15:13.8833|DEBUG|lightstreamer.session|sessionStatusChanged 11, 11
2020-08-25 10:15:13.8833|DEBUG|lightstreamer.session|Session state change (4): CREATING -> SLEEP
2020-08-25 10:15:13.8980|DEBUG|lightstreamer.session| phasing : 2 - 2
2020-08-25 10:15:13.8980|INFO|lightstreamer.protocol|Protocol dismissed
2020-08-25 10:15:13.8980|DEBUG|lightstreamer.session|Status timeout in 0 [currentRetryDelay] due to network.error
>>>>>>>>>>>>>>>>>> DISCONNECTED:WILL-RETRY -
2020-08-25 10:15:13.9610|DEBUG|lightstreamer.session|Timeout event [currentRetryDelay] while SLEEP cause=network.error
2020-08-25 10:15:13.9610|DEBUG|lightstreamer.session|Timeout: new session
2020-08-25 10:15:13.9610|INFO|lightstreamer.session|Closing session new.network.error
2020-08-25 10:15:13.9610|DEBUG|lightstreamer.subscribe|SubscriptionManager sessionAlive set to false.
2020-08-25 10:15:13.9610|INFO|lightstreamer.subscribe|Reset message handler
2020-08-25 10:15:13.9610|DEBUG|lightstreamer.subscribe|Aborting pending messages
2020-08-25 10:15:13.9610|DEBUG|lightstreamer.session|SessionManager state change: POLLING_HTTP -> POLLING_HTTP

Any ideas?

Dario Crivelli

Hi,
I have moved this post back to the relevant thread.

It is no surprise that, by limiting the connection to http polling nothing has changed.
In fact, in your case, there is no answer from the Server since the initial connection, before the client ever tries websocket or http streaming.
I see that the client receives a "Socket error" message from the low-level "DotNetty" library.

Unfortunately, no further indication is logged.
For this reason, if you can manage to get a packet capture, this may provide some clue.
Otherwise, can you try a simple manual request from the same context of your application, to see what happens?
For instance, you can just issue https://push.cityindex.com/