Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sMg74-003oQG-G4 for pgsql-general@arkaria.postgresql.org; Thu, 27 Jun 2024 03:47:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sMg72-007w79-T1 for pgsql-general@arkaria.postgresql.org; Thu, 27 Jun 2024 03:47:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sMg72-007w71-Af for pgsql-general@lists.postgresql.org; Thu, 27 Jun 2024 03:47:56 +0000 Received: from mail-vk1-xa2f.google.com ([2607:f8b0:4864:20::a2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sMg6z-003KIb-A2 for pgsql-general@lists.postgresql.org; Thu, 27 Jun 2024 03:47:55 +0000 Received: by mail-vk1-xa2f.google.com with SMTP id 71dfb90a1353d-4ef6e79b47dso662228e0c.0 for ; Wed, 26 Jun 2024 20:47:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719460072; x=1720064872; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fjDCN612mlE0Wz5k5SCSlGY2N78z8mAxV/mu3gs1UGI=; b=FMXsFjk9unQtxwHnfKPflYrYE2Jg5ucI+Tdt9HWrZW5cUp9rGRp1S2camFvO8p0akF Q/kbiwtM9py/qzsIbCfPoZB6uhSpfUnIAGfyPArkEoVE4V0a8DgRHADGe6HznHddRDdz aYHG7dOFAPPWZxzKK9EXQVIyyl0BNtWVKKwk8ShWovSUBOGAz5kZKzt8aejifBi5FQdU 5bkIgRn80er380//Qytmxx1948CGesfaA1DjgdRzqtwsSzwnN9darztEG60sXDNbDrG9 RCCYD3PJB/X5EoPNACRvoRS1PvrFdt8fLfXog+bGLEQtsGCZkRRizsKpXc8XR/b9Xf8c X40w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719460072; x=1720064872; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fjDCN612mlE0Wz5k5SCSlGY2N78z8mAxV/mu3gs1UGI=; b=CWW8BEhFExtxPWCxwTUjdRnktODg5uFD41loBz/juK5C73+37sb5dtzGEPO8+HWHfv gJeag2TRPNVY+FDwqrK6WE/Qy204PWKtMHSGSWMAU4vpwD+OSh/JWthPs3kRQCJQ8pZH 1qGnJFZh7JW6iVWZQLn+0MNWJTYgQ/qkm2CDBtEocLevARvSArMC47pbP5JTs6LlbOn5 J2jzidv5FfCJ5IOAvPv71VqObjIxNPsyRUe9GryWrw6buUvsEHmDxJ6xrIjb+kmXTziM FErpiF5ahS/ls5iFktsVc3Id2Ow1cFPGGX2aHvUBAcL6wEDcN/AuawvsA6FYAZKoExiP qF+w== X-Gm-Message-State: AOJu0YzHfsTPJd9lsscMX7kcB0NLk9QHQGWsh0srIxltAU+dqDw290Q6 KsnwdiVWkiIOp++v+ScZ20hcyyBsUH30LsPPoNj8ZGWMeJsCk0cPaNGjGA8vG1drnpj+V1o7GHe rp0D8fGAs+k79t9nf37RPAOEn5RQ= X-Google-Smtp-Source: AGHT+IEOodmJK/Xcx7e9iNesizdcqldGzFgVNfwIoXqy+BHMHU3XiBDhuICkq4OtEak02qdvzZ8GiEx4iVru1P+M6sw= X-Received: by 2002:a05:6122:601a:b0:4eb:ddd:4b95 with SMTP id 71dfb90a1353d-4f283a23fb4mr283452e0c.0.1719460071925; Wed, 26 Jun 2024 20:47:51 -0700 (PDT) MIME-Version: 1.0 References: <842a688946204561ad0787606a644ecf@onalaskawi.gov> In-Reply-To: <842a688946204561ad0787606a644ecf@onalaskawi.gov> From: Kashif Zeeshan Date: Thu, 27 Jun 2024 08:47:41 +0500 Message-ID: Subject: Re: Dropping connections To: "Tarras, Tim" Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000caf086061bd6fe8a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000caf086061bd6fe8a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Tarras Please refer to the following guide where connection was working fine with PG and EPAS. https://www.enterprisedb.com/docs/partner_docs/EsriArcGISProandEsriArcGISEn= terprise/04-ConfiguringEsriArcGISProandEsriArcGISEnterprise/ Regards Kashif Zeeshan On Wed, Jun 26, 2024 at 10:45=E2=80=AFPM Tarras, Tim wrote: > Hello, > > I am having problems with loosing connection to a postgresql database wit= h > ESRI ArcGIS Pro. Below is what I put on the ESRI community forums but als= o > wanted to post here to see I can get a resolution to this problem. Thank > you for any help you can provide. > > Tim > > I'm not sure if this is the right place but, I am having an issue with > enterprise Database connections dropping to my computer. If I work with > ArcPro on the server the connections do not drop. We also made a connecti= on > directly from my computer using pgAdmin and will not lose connection even > when I loose it in Pro. > > My system is as follows: > > 1. ArcGIS Enterprise 11.2 Single machine deployment. Server has 32GB > of memory > 2. ArcgisPro 3.3.0 > 3. Postgres 15.4 Downloaded from ESRI and on a separate server from > enterprise. Server has 12 cores and 32GB of memory > 4. Both servers are running Windows Server 2022 datacenter > Version 21H2. > > When the connection drops I get the following message: > > Underlying DBMS error [no connection to the server::SQLSTATE=3D=C3=A5] > [xxxxxxx.xxx.GDB_Items][STATE_ID =3D 0] > > X's replace actual names. > > Working with ESRI we found the following information in the logs : > > "*An existing connection was forcibly closed by the remote host*" where > host is the PostgreSQL Server and "*FATAL: terminating connection due to > administrator command*". The following PostgreSQL documentation provides > more information about the same (https://www.postgresql.org/message-id/56= 65.1202148155%40sss.pgh.pa.us > [postgresql.org] > > ). > > At this time IT says it is not a fire wall issue as there are no rules > setup for dropping connections. We are at a loss as to what the culprit i= s. > > I will also be posting this in PostgreSQL community to get their input. > > Thank you for your help with this. > > > > > This email and any files transmitted with it are confidential and are > intended solely for the use of the individual or entity to which they are > addressed. If you have received this email in error, please respond to th= e > sender and delete the material from any computer and/or server. The City = of > Onalaska is subject to Wisconsin Statutes relating to public records. > Emails sent or received by City employees are subject to these laws. Unle= ss > otherwise exempted from the public records law, senders and receivers of > City email should presume that the emails are subject to release upon > request, and to state record retention requirements. > --000000000000caf086061bd6fe8a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Tarras

Please refer to the following= guide where connection was working fine with PG and EPAS.

<= div class=3D"gmail_quote">
On Wed, Jun= 26, 2024 at 10:45=E2=80=AFPM Tarras, Tim <ttarras@onalaskawi.gov> wrote:

Hello,

I am having problems with loosing connection to a postgresql database wi= th ESRI ArcGIS Pro. Below is what I put on the ESRI community forums but al= so wanted to post here to see I can get a resolution to this problem.=C2=A0= Thank you for any help you can provide.

Tim

I'm not sure if this is the right place but, I am having an issue wi= th enterprise Database connections dropping to my computer. If I work with = ArcPro on the server the connections do not drop. We also made a connection= directly from my computer using pgAdmin and will not lose connection even when I loose it in Pro.=C2=A0=C2=A0

My system is as follows:

  1. ArcGIS Enterprise 11.2 Single machine deployment. Server has 32GB of memory=
  2. ArcgisPro 3.3.0
  3. Postgres 15.4 Downloaded from ESRI and on a separate server from enterprise= . Server has 12 cores and 32GB of memory
  4. Both servers are running Windows Server 2022 datacenter Version=C2=A021H2.<= u>

When the connection drops I get the following message:

Underlying DBMS error [no connection to the server::SQLSTATE=3D=C3=A5] [= xxxxxxx.xxx.GDB_Items][STATE_ID =3D 0]

X's replace actual names.

Working with ESRI we found the following information in the logs :

"An existing= connection was forcibly closed by the remote host" wh= ere host is the PostgreSQL Server and "FATAL: terminating connection due to administrator command". The following PostgreS= QL documentation provides more information about the same (https://www= .postgresql.org/message-id/5665.1202148155%40sss.pgh.pa.us [postgresql.org]).

At this time IT says it is not a fire wall issue as there are no rules s= etup for dropping connections. We are at a loss as to what the culprit is.<= u>

I will also be posting this in PostgreSQL community to get their input.<= u>

Thank you for your help with this.

=C2=A0

=C2=A0

This email and any files transmitted with it are confidential and are inten= ded solely for the use of the individual or entity to which they are addres= sed. If you have received this email in error, please respond to the sender= and delete the material from any computer and/or server. The City of Onalaska is subject to Wisconsin Statu= tes relating to public records. Emails sent or received by City employees a= re subject to these laws. Unless otherwise exempted from the public records= law, senders and receivers of City email should presume that the emails are subject to release upon request, = and to state record retention requirements.
--000000000000caf086061bd6fe8a--