From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | "Bazan, Hernan" <hernan(dot)bazan(at)intel(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC failing due to networking issues |
Date: | 2016-05-24 12:49:13 |
Message-ID: | CADK3HHKCh7cs6NpBxQCYdWmpJ6+cFXyi5E5kqwphgbsoSYcqgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
My guess is the keys are not correct for the validating ssl connection. Do
you have the stack trace by chance ?
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
On 23 May 2016 at 20:48, Bazan, Hernan <hernan(dot)bazan(at)intel(dot)com> wrote:
> We are facing a problem on a customer where (apparently) there are
> networking issues.
>
> Basically, we have a master DB with several hot_standby slaves, some on
> the same geo than the master, some on different geo. The application we run
> uses two JDBC connection pools, one read-only to the local DB replication,
> one write-only to the master DB.
>
> The odd thing on this case is that the replication process is working, the
> slave is up to date with the master, but the JDBC connection to the master
> fails during the handshake process, with a fatal (48) error.
>
> Enabling trust connections on the master for the given host, and disabling
> SSL validation (&sslfactory=org.postgresql.ssl.NonValidatingFactory) we can
> connect successfully.
>
> We need a way to debug this issue and understand how the replication
> connection works ok and the JDBC doesn’t. What next steps do you recommend?
>
>
>
>
>
> Thanks
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2016-05-24 13:15:00 | Re: JDBC client hangs on socketRead() |
Previous Message | Dave Cramer | 2016-05-24 12:47:01 | Re: JDBC client hangs on socketRead() |