Connection forcibly closed remote server error.
Hi, We are getting this error when transferring data using COPY command or running workflow for huge data. We are using Password Authentication(LDAP) "Connection forcibly closed remote server" Can someone help how we can avoid this? Regards, Aditya.
Re: Connection forcibly closed remote server error.
Forgot to mention. The error comes intermittently. It is not consistent. Observation is that it comes when a connection has to process a larger data set. On Wed, Feb 15, 2023 at 5:43 PM aditya desai wrote: > Hi, > We are getting this error when transferring data using COPY command or > running workflow for huge data. We are using Password Authentication(LDAP) > > "Connection forcibly closed remote server" > > Can someone help how we can avoid this? > > > Regards, > Aditya. >
Re: Connection forcibly closed remote server error.
aditya desai writes: > We are getting this error when transferring data using COPY command or > running workflow for huge data. We are using Password Authentication(LDAP) > "Connection forcibly closed remote server" Network timeout perhaps? If so, setting more-aggressive TCP keepalive parameters might help. regards, tom lane
Re: Connection forcibly closed remote server error.
On Wed, Feb 15, 2023 at 7:13 AM aditya desai wrote: > Hi, > We are getting this error when transferring data using COPY command or > running workflow for huge data. We are using Password Authentication(LDAP) > > "Connection forcibly closed remote server" > Are you sure that that is the exact wording? It doesn't sound like grammar that would be used for an error message. Or did you perhaps translate it to English from a localized error message? Is that error reported by the client, or in the server log? Whichever end that is, what does the other end say? Cheers, Jeff
Re: Connection forcibly closed remote server error.
Hi Jeff, Apologies. Here is how the message actually looks like. could not receive data from client: An existing connection was forcibly closed by the remote host. All links from Google pointing towards Connection Pooling. However it has been implemented from the application side. Regards, Aditya. On Thu, Feb 16, 2023 at 12:07 AM Jeff Janes wrote: > On Wed, Feb 15, 2023 at 7:13 AM aditya desai wrote: > >> Hi, >> We are getting this error when transferring data using COPY command or >> running workflow for huge data. We are using Password Authentication(LDAP) >> >> "Connection forcibly closed remote server" >> > > Are you sure that that is the exact wording? It doesn't sound like grammar > that would be used for an error message. Or did you perhaps translate it > to English from a localized error message? > > Is that error reported by the client, or in the server log? Whichever end > that is, what does the other end say? > > Cheers, > > Jeff > >
Re: Connection forcibly closed remote server error.
Em qua., 15 de fev. de 2023 às 15:55, aditya desai escreveu: > Hi Jeff, > Apologies. Here is how the message actually looks like. > > could not receive data from client: An existing connection was forcibly > closed by the remote host. > It looks like a Microsoft tool message. Perhaps .NET https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/tls-exist-connection-closed I think that Postgres has nothing to do with the problem. regards, Ranier Vilela >
