Uploaded image for project: 'JBoss Remoting'
  1. JBoss Remoting
  2. JBREM-947

ConnectionValidator hangs when server dies



    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.2.2.SP7
    • Fix Version/s: 2.4.0.CR2 (Pinto)
    • Component/s: None
    • Labels:


      If the connection between client and server is pulled (pull the real cable) or the entire server suddenly dies, then the connection won't be closed from the server (unlike a kill -9 of the server where the OS will terminate that processses connections), so the client making the write() or read() on the socket won't receive an exception.

      In the eyes of TCP the connection is still alive and the read/write will block until the socket timeout is reached.

      Typically the socket timeout will be much higher than the desired failure detection time (the validation interval), but currently failure will never be detected in this situation before the socket timeout time.

      Remoting should not be dependent on the socket timeout for failure detection, the connetion validation and socket timeout should be possible to be configured separately.

      E.g. you might want to configure a socket timeout of 60 seconds, but a connection validation frequency (ping) of 5 seconds. Currently this is not possible.

      The current implementation gives inconsistent behaviour depending on how the server died - i.e. whether the process died (e.g. kill -9) or the cable was pulled or the entire server disappeared.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  ron_sigal Ronald Sigal
                  timfox Tim Fox
                • Votes:
                  0 Vote for this issue
                  1 Start watching this issue


                  • Created: