1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Communication Error 8409 7175 When On A Wan Using Open Client

Discussion in 'Development' started by Clueless, Jul 22, 2017.

Thread Status:
Not open for further replies.
  1. Clueless

    Clueless New Member

    I have a C# program using an open client connection directly to a CentOs 6.5 Linux OpenEdge 10.2B patch 8 appserver -> database (does not use the nameserver & operating mode is state-free).

    All works well when on a LAN.

    But when the Linux server was moved from a LAN to out-of-state data center, then started getting intermittent "Communication Error. Contact your system administrator. Communication layer message: Client Communication Failure - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (8409) . (7175)."

    Data center has 20 MB upload/download network bandwidth as well as the client PC's office network.

    Looked at KBase 000035944 and it recommended adding the following file in the executable directory (the application is named surveyor.exe, so created a file named surveyor.exe.config)

    ========================snip============================
    KBase 000035944 excerpt:

    To manually disable the socket time please use one of the following methods:
    • In the .NET application set the undocumented property Progress.Open4GL.RunTimeProperties.SocketTimeout to 0 before the connection is established.
    • In the application configuration file (e.g. app.config) set the socket timeout to 0. For example:

    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
    <appSettings>
    <add key="PROGRESS.Session.SocketTimeout" value="0" />
    </appSettings>
    </configuration>

    ========================snip============================

    But this did not help.

    To test, when we add SSL capability to the C# client and appserver, then the communications error occurrences double.

    Also moved the database to the Amazon Cloud and got the same communication error.

    Thanks in advance for any help.
     
  2.  
  3. Cringer

    Cringer ProgressTalk.com Moderator Staff Member

    You don't need more than one thread on this so I'll leave the one over in the DBA forum open.
     
Thread Status:
Not open for further replies.

Share This Page