Menu ▾ ▴

#871 Session negotiation fails due to wrong timeouts

Core 1.0
closed-fixed
Stefan Rossbach
None
5
2019-12-02
2016-09-12
Bernd Sahre
No

Description
In Saros are various configuration of PCs (for example: Pool-PC to own Notebook) where the Connection is closed during the Invitation Process. After the Host invitate, the client clicks next on the appearing window. Then Saros tries to establish a connection; since nothing happens ~40 seconds the connection refused with the error message Invitation was canceled by the remote user ceacuse of an error on his/her side: Invitation was not accepted.
There are some setting which has always, and some who has never this error.
It seems that there is a timeout on hostside which terminates the session invitation.

Issue: The connection attempt can vary between several seconds up to 1 minute.

This is ignored in the session negotiation as all timeouts are lower than 1 minute. To be more specific: 30 seconds by default.

Discussion

  • Stefan Rossbach

    Stefan Rossbach - 2016-09-12
    • status: open --> closed-fixed
    • Group: 14.10.31 --> OTHER
     

  • Stefan Rossbach

    Stefan Rossbach - 2016-09-12

    This isnt IntelliJ related. I will post a fix in the next 5 minutes.

     

  • Stefan Rossbach

    Stefan Rossbach - 2016-09-12
    • summary: [Intellij] Remote-Error: Invitation not accepted --> Session negotation fails due to wrong timeouts
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,4 +1,8 @@
 **Description**
-In Saros for Intellij are various configuration of PCs (for example: Pool-PC to own Notebook) where the Connection is closed during the Invitation Process. After the Host invitate, the client clicks next on the appearing window. Then Saros tries to establish a connection; since nothing happens ~40 seconds the connection refused with the error message *Invitation was canceled by the remote user ceacuse of an error on his/her side: Invitation was not accepted.*
+In Saros are various configuration of PCs (for example: Pool-PC to own Notebook) where the Connection is closed during the Invitation Process. After the Host invitate, the client clicks next on the appearing window. Then Saros tries to establish a connection; since nothing happens ~40 seconds the connection refused with the error message *Invitation was canceled by the remote user ceacuse of an error on his/her side: Invitation was not accepted.*
 There are some setting which has always, and some who has never this error.
 It seems that there is a timeout on hostside which terminates the session invitation.
+
+Issue: The connection attempt can vary between several seconds up to 1 minute. 
+
+This is ignored in the session negotiation as all timeouts are lower than 1 minute. To be more specific: 30 seconds by default.
    • status: closed-fixed --> open-fixed
    • assigned_to: Stefan Rossbach
     

  • Stefan Rossbach

    Stefan Rossbach - 2016-09-12
    • summary: Session negotation fails due to wrong timeouts --> Session negotiation fails due to wrong timeouts
     

  • Stefan Rossbach

    Stefan Rossbach - 2016-09-12

    Should be applied within the next hour.

    http://saros-build.imp.fu-berlin.de/gerrit/#/c/3128/

     

    • Franz Zieris

      Franz Zieris - 2016-09-12

      No need to rush :)

       

  • Franz Zieris

    Franz Zieris - 2016-09-23
    • status: open-fixed --> pending-fixed
     

  • Franz Zieris

    Franz Zieris - 2016-09-23

    Submitted as [de690f]

     

    Related

    Commit: [de690f]

  • Stefan Rossbach

    Stefan Rossbach - 2017-04-13
    • Group: OTHER --> Core 1.0
     

  • tobous

    tobous - 2019-12-02
    • Status: pending-fixed --> closed-fixed
     

Log in to post a comment.