Port with Established connection Plus a Listener (not multi)

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Port with Established connection Plus a Listener (not multi)

  • Creator
    Topic
  • #51657
    Rob Lindsey
    Participant

      All,

      I am at a loss here.  I have an inbound thread (not a multi-server) that is listening on port 62670 but when the external client connects to this port I get both an established connection plus a Listener.

      /qdx/qdx5.3/integrator/client10> netstat -an | grep 62670

      tcp4       0      0  *.62670                *.*                    LISTEN

      tcp4    1516      0  192.168.106.5.62670    128.64.0.17.16401      ESTABLISHED

      I have not seen this happen before and I need to get it fixed because according to the client they can not send data to this port and get a ACK back.  Here is how I have the comms section setup…

         { PROTOCOL {

             { CA_FILE {} }

             { CA_PATH {} }

             { CERT_FILE {} }

             { CLOSE 0 }

             { CONTROLMSGS 0 }

             { COPYCLIENTIPP 0 }

             { HOST {} }

             { ISMULTI 0 }

             { ISSERVER 1 }

             { IS_SSL 0 }

             { MAXCLIENT 0 }

             { MAXOBQD 0 }

             { MAXPREXLTQD 0 }

             { MODE {} }

             { PASSWORD {} }

             { PDLNAME mlp_tcp.pdl }

             { PDLTYPE tcp-server }

             { PORT 62670 }

             { PRIVATE_KEY {} }

             { RECONNECT 1 }

             { REOPEN 5 }

             { TYPE pdl-tcpip }

         } }

      TIA for any and all help.

      Rob Lindsey

    Viewing 2 reply threads
    • Author
      Replies
      • #71133
        James Cobane
        Participant

          Rob,

          One suggestion I would have is to not use a port number that is in the ephemeral range as a server port.  I would suggest a port number below 32768.

          Jim Cobane

          Henry Ford Health

        • #71134
          Rob Lindsey
          Participant

            Here is another HINT that I have found in the ERR log…

            setsockopt NODELAY on socket failed: Invalid argument

            I get this about every 3 minutes.

            Thanks again.

            Rob

          • #71135
            Jim Kosloskey
            Participant

              Rob,

              I would agree with Jim Cobane – change your port to one lower than the base of your system’s ephemeral range.

              This shows you have configured to LISTEN on port 62670 but since that is in the ephemeral range, you have actually ESTABLISHED the connection on port 16401.

              Give that a try and see if that does not correct the issue.

              email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.