Problem with Multi-Client Server – Cloverleaf 5.6

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Problem with Multi-Client Server – Cloverleaf 5.6

  • Creator
    Topic
  • #51587
    Troy Morton
    Participant

      See the attached screen shot.

      I have a multi-client thread set up, however, when I bounce my Server thread, I get the error, “Cannot bind on port xxxxx, address already in use.”.  When I bounce the Server thread again, all connections come back up with no problems.

      Server thread: troy_oru_recv

      Client thread1: troy_oru_send

      Client thread2: troy_orm_send

      I have even tried putting my two client threads on different servers than the Server thread and this behaivor still occurs.

      Anyone using Multi-Client Server that can tell me what I might be doing wrong?

      Thanks!!

    Viewing 2 reply threads
    • Author
      Replies
      • #70873
        Tom Rioux
        Participant

          I am assuming you are set up as “Muti-Server” in the NetConfig set up.  It seems to me that if the set up is correct, as you explained, then if the server thread was in an error state then the client threads wouldn’t be showing up.   It appears that they may be connecting to another server or another localhost connection somewhere. Just a guess.

          Can you show some snapshots of your protocol settings on all three threads?

          Tom

        • #70874
          Troy Morton
          Participant

            Hi Thomas,

            Thanks for your reply!

            I thought that same thing you did .. that there was another localhost listener on this port, but I verified that when I shut down my receiver process and run “netstat -an | grep ” there is nothing listening on the port I’m using.

            I have attached the NetConfig screen shots for all three threads.

            Troy

          • #70875
            Bob Richardson
            Participant

              Troy and company,

              We had this problem when we had another server thread configured with the same port in a different site (we are multi-site).  It was not a Multi-Connect type thread, just plain ole mlp_tcp TCP/IP.  I would look for the same port already configured on another thread perhaps in a different site.

              Going forward, we implemented a ksh/tcl script to hunt down duplicate port use in our sites (that is for server connections).  This alerts us when we reuse ports.  

              If you would like our script let me know – you may have to tweak it a bit.

              Good luck; good hunting!

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