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:/
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,
Adity
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 wor
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
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 w
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.
