Clovertech

Connect Error (WSAEALREADY)

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Connect Error (WSAEALREADY)

  • Creator
    Topic
  • January 16, 2006 at 8:28 pm #48258
    Arslan Khan
    Participant

      Hi Guys,

      I am trying to migrate my existing interfaces from Unix environment to Windows. All my interfaces are working ok on new platform except one ADT interface. I am able to establish connection with my client but this connection drops after a while and my thread status changes to “opening”.

      when I turned on the process logs, I noticed following log entries:

      [pdl :PDL :DBUG/0:    nfs_adtoe] tcp-client: attempting connect to: 100.199.10.11:5201

      [pdl :PDL :INFO/0:    nfs_adtoe] tcp-client: connect error (WSAEALREADY)

      I have placed a call to network support to check any potential problems with firewall issues.

      Any ideas what this “WSAEALREADY” stands for? Does any one ever come across this error?

      Any insight on this issue is highly appreciable.

      Thanks.

      Arslan Khan

    • Creator
      Topic
    Viewing 1 reply thread
    • Author
      Replies
      • January 16, 2006 at 9:18 pm #58191
        Jim Kosloskey
        Participant

          Arslan,

          I seem to recall that means already connected. It is possible that when the trading partner dropped your connection it did not completely sever the connection.

          It looks like Cloverleaf is trying to reconnect but the reconnect is being refused. Sometimes a tcp/ip connection can be configured to refuse reconnections maybe that is happening.

          Thanks,

          Jim Kosloskey

          email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

        • January 17, 2006 at 10:08 pm #58192
          Arslan Khan
          Participant

            Thanks for your input Jim. But I still think that this is because of a firewall. Some how firewall is severing the connection between my client and the engine, and re-connects are failing because client thinks the connection is still active. Any idea how to tackle this situation?

            Arslan

        • Author
          Replies
        Viewing 1 reply thread
        • The forum ‘Cloverleaf’ is closed to new topics and replies.