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 1sRS7i-00FSxZ-85 for pgsql-general@arkaria.postgresql.org; Wed, 10 Jul 2024 07:52:22 +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 1sRS7f-002ydw-Hk for pgsql-general@arkaria.postgresql.org; Wed, 10 Jul 2024 07:52:19 +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 1sRS7f-002ydl-1y for pgsql-general@lists.postgresql.org; Wed, 10 Jul 2024 07:52:19 +0000 Received: from mail-ua1-x930.google.com ([2607:f8b0:4864:20::930]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sRS7b-001Kvy-Uc for pgsql-general@lists.postgresql.org; Wed, 10 Jul 2024 07:52:17 +0000 Received: by mail-ua1-x930.google.com with SMTP id a1e0cc1a2514c-81014df3028so1821131241.3 for ; Wed, 10 Jul 2024 00:52:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720597935; x=1721202735; 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=yLDgykRUsXeuQvJw7rR0PGA2DI0zMFb15BQBg0Jvs4Q=; b=IV1SFjMdpJdaIQV+A3air/cXKWXiyhmWfR2UGCe8xLIXqqvLdD8fn8H35PhdmdFykx Giww0Zp2rFzS3+fWn66A8zg0k+qrUjmq+vAfxBG9FnjLskMgLXCbm17H8RXVlgie5VmB 0109Q95GzYnMTo1E2rnGUWWS+vkzNEPj1S4UlmJYQBmb4THfadih/0FOKUrOfLBzsFYR /g6noqOAPFlcwIIunPT+l/DNE1pLLsoPpjhN5SgQl3F2lBIEHzGxxU68E2MQ8LxDlwFm 5CCaDwKDIc5xngoI+9pOz9wWrS2P7c5xbNoaj2X0N5oZGdaYDCNsJs73DVed0nILmy7O yXlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720597935; x=1721202735; 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=yLDgykRUsXeuQvJw7rR0PGA2DI0zMFb15BQBg0Jvs4Q=; b=bh4ku1ksawZITCGJ2O6m6eTPBYQD+NVEWkwIuXczBDP6SxR3YtXQp4z+ENCO6CY5Fo C0DSDHk0jhbSDPiXkRXc+K1K/GqB2Odw3INx4diXCX+fzB96B7BCYrq3a6p/i1M/WFRP WPbcKdkL7hI97onBVDmLJ/41wjg1i8fQUHry4mGwBjeYSL0Tr7bIRc1y0gont9/Kw+j0 IqRk/B/iIyDMMk/Epg78f7mbfpedKKmBho41Orv8U3e6K7lKCRMt4ctsabiiCmXZg0bJ nMrsTeP4PnR3vV7IUFWcujuqi34Ht1vNkJt9s2PLUAmGN7oorIl9/0JHjbRz+AHkdIrI aq5A== X-Gm-Message-State: AOJu0Yw7GCoH3meatBmPy+ODswG0eEQfF6vWsSWFUive+TOdGVR/2AVL oErpQv/fE94vTK6xM78gQ9vtaq6uq1CvIY7CTpUY4vgksMA6OZ0DnqZLZq3d2tY2OH+A2f8vqoV sAkeLnStrnJsWe7OaqgkrWwugTyY= X-Google-Smtp-Source: AGHT+IGggM89JjVL4387nb8cpUdhhBznKUDjuxh453mHVLXxn8zqLDUAmo6vfd7ZPlzY+jjUFhNCi2sRAQCQHyDGMec= X-Received: by 2002:a05:6102:4405:b0:48f:79de:909e with SMTP id ada2fe7eead31-490321a413amr5901676137.18.1720597934558; Wed, 10 Jul 2024 00:52:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kashif Zeeshan Date: Wed, 10 Jul 2024 12:52:03 +0500 Message-ID: Subject: Re: Postgres :- Could not open R2DBC Connection To: vimal va Cc: pgsql-general@lists.postgresql.org, vimal.arumugam@wipro.com Content-Type: multipart/alternative; boundary="000000000000b0d6d2061cdfec85" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b0d6d2061cdfec85 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Can you check the following. 1. The machine 10.0.202.121 is accessible. 2. Check the firewall settings. 3. Check the pg_hha.conf Settings. Regards Kashif Zeeshan On Wed, Jul 10, 2024 at 12:48=E2=80=AFPM vimal va wrot= e: > Dear team , > > This is Vimal from WIpro. We are using Postgres 14 , while connecting > postgres from application we are getting "*Could not open R2DBC > Connection for transaction;" error in pod . *We have increased the max > number of connections in postgres from 100 to 1000 , still we are facing > the same error. > I have pasted below the error for reference. Please help us on this issue > > Thanks, > Vimal. > > > > > > > > *reactor.core.Exceptions$ErrorCallbackNotImplemented: > org.springframework.transaction.CannotCreateTransactionException: Could n= ot > open R2DBC Connection for transaction; nested exception is > io.r2dbc.postgresql.PostgresqlConnectionFactory$PostgresConnectionExcepti= on: > Cannot connect to 10.0.202.121/ > :5432Caused by: > org.springframework.transaction.CannotCreateTransactionException: Could n= ot > open R2DBC Connection for transaction; nested exception is > io.r2dbc.postgresql.PostgresqlConnectionFactory$PostgresConnectionExcepti= on: > Cannot connect to 10.0.202.121/ > :5432 at > org.springframework.r2dbc.connection.R2dbcTransactionManager.lambda$null$= 5(R2dbcTransactionManager.java:227) > at > reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnE= rrorResume.java:94) > at > co.elastic.apm.agent.reactor.TracedSubscriber.onError(TracedSubscriber.ja= va:126) > at > reactor.core.publisher.MonoFlatMap$FlatMapMain.onError(MonoFlatMap.java:1= 72) > at > co.elastic.apm.agent.reactor.TracedSubscriber.onError(TracedSubscriber.ja= va:126)* > > --000000000000b0d6d2061cdfec85 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0

Can you check the following.

1. The machine 10.0.202.121 is accessible.=C2=A0
2. Check the firewall settings.
3. Check the pg_hha.conf = Settings.

Regards
Kashif Zeeshan



On Wed, Jul 10, 2024 at 12:48=E2=80=AFPM vima= l va <vimal.va@gmail.com> w= rote:
Dear team ,

This is Vimal fro= m WIpro. We are using Postgres 14 , while connecting postgres from applicat= ion we are getting "Could not ope= n R2DBC Connection for transaction;"=C2=A0 error in pod . We have = increased the max number of connections in postgres from 100 to 1000 , stil= l we are facing the same error.
I have pasted below the error for reference. Please help us on this= issue

=
Thanks,
Vimal.

reactor.core.Exceptions$ErrorCallbackNot= Implemented: org.springframework.transaction.CannotCreateTransactionExcepti= on: Could not open R2DBC Connection for transaction; nested exception is io= .r2dbc.postgresql.PostgresqlConnectionFactory$PostgresConnectionException: = Cannot connect to 10.0.202.121/<unresolved>:5432
Caused by: org.springframework.transaction.CannotCre= ateTransactionException: Could not open R2DBC Connection for transaction; n= ested exception is io.r2dbc.postgresql.PostgresqlConnectionFactory$Postgres= ConnectionException: Cannot connect to 10.0.202.121/<unresolved>:5432<= /span>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 at org.springframework.r2dbc.connection.R2dbcTransactionManage= r.lambda$null$5(R2dbcTransactionManager.java:227)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 at reactor.co= re.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnErrorResume.j= ava:94)
=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 at co.elastic.apm.agent.reactor.TracedSubscriber.onEr= ror(TracedSubscriber.java:126)
= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 at reactor.core.publisher.MonoFl= atMap$FlatMapMain.onError(MonoFlatMap.java:172)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 at co.elastic.a= pm.agent.reactor.TracedSubscriber.onError(TracedSubscriber.java:126)=
=C2=A0

--000000000000b0d6d2061cdfec85--