Results 1 to 8 of 8

Hybrid View

  1. #1
    Okay, made it past the first issue. Same network, but their might be some network segregation going on. Adding the proxy to the computer made it so the client will now find/connect successfully. However, the connection closes after ~30 seconds with a PushConnException:

    {"The underlying connection was closed: The connection was closed unexpectedly."} Lightstreamer.DotNet.Client.PushConnException


    On the server, they saw the SSL handshake succeed but and then the connection closed shortly after that.

    debug logs:

    23-Jan-14 16:08:25,364|DEBUG|LightstreamerLogger.connections | Lightstreamer HTTPS Server|Socket accept on 10.x.x.20:58596
    23-Jan-14 16:08:25,424|DEBUG|ghtstreamerLogger.connections.s sl|IO SSL HANDSHAKE SELECTOR 1|Handshake completed on socket Lightstreamer HTTPS Server; selected cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
    23-Jan-14 16:08:25,424|INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 5 |Accepted HTTPS connection on Lightstreamer HTTPS Server from 10.x.x.20:58596
    23-Jan-14 16:08:30,236|DEBUG|LightstreamerLogger.connections | Lightstreamer HTTPS Server|Socket accept on 10.x.x.20:60089
    23-Jan-14 16:08:30,380|DEBUG|ghtstreamerLogger.connections.s sl|IO SSL HANDSHAKE SELECTOR 1|Handshake completed on socket Lightstreamer HTTPS Server; selected cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
    23-Jan-14 16:08:30,380|INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 6 |Accepted HTTPS connection on Lightstreamer HTTPS Server from 10.x.x.20:60089
    23-Jan-14 16:08:46,305|INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 1 |Closed HTTPS connection on Lightstreamer HTTPS Server from 10.x.x.20:58596
    23-Jan-14 16:08:56,376|INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 8 |Closed HTTPS connection on Lightstreamer HTTPS Server from 10.x.x.20:60089


    (slight ip address obfuscation, even tho it is private)

    Also, when i look for all exceptions there is a socketException that is being thrown: System.net.Sockets.SocketError.AccessDenied
    message: An attempt was made to access a socket in a way forbidden by its accessor permissions

    Any suggestions on next steps?

  2. #2
    Administrator
    Join Date
    Feb 2012
    Location
    Milano
    Posts
    716
    Hi Eric,

    The unexpected closures are due to normal behavior of the server that after a certain period of inactivity closes the connection.
    Thus, it is possible that the two connections shown in the log have been opened but then never used?

    I don't think that the "AceessDenied" exception is directly linked to the situation seen above; perhaps it can cause a blockage in the logic flow of the application and thus prevent subsequent requests to Lightstreamer?
    By the way, the problem of "AccessDenied" should be linked to problems of permissions configuration in the client application.

 

 

Similar Threads

  1. Mixing SSL and non-SSL
    By kpturner in forum General
    Replies: 2
    Last Post: March 2nd, 2015, 10:19 AM
  2. Lightstreamer WinRT Client Lib is Available
    By Alessandro in forum Client SDKs
    Replies: 0
    Last Post: December 20th, 2012, 11:04 AM
  3. create_session related issue.
    By Sathyaayyanar in forum Adapter SDKs
    Replies: 5
    Last Post: August 24th, 2010, 09:32 AM
  4. SetDomain setLSHost related issue
    By Sathyaayyanar in forum Client SDKs
    Replies: 1
    Last Post: July 30th, 2010, 01:32 PM
  5. Trying to run LS through Https / SSL
    By wmolde in forum Client SDKs
    Replies: 2
    Last Post: April 18th, 2007, 03:40 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 02:01 PM.