Re: JDBC failing due to networking issues - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: JDBC failing due to networking issues
Date
Msg-id CADK3HHKCh7cs6NpBxQCYdWmpJ6+cFXyi5E5kqwphgbsoSYcqgw@mail.gmail.com
Whole thread Raw
In response to JDBC failing due to networking issues  ("Bazan, Hernan" <hernan.bazan@intel.com>)
Responses Re: JDBC failing due to networking issues  ("Bazan, Hernan" <hernan.bazan@intel.com>)
List pgsql-jdbc
My guess is the keys are not correct for the validating ssl connection. Do you have the stack trace by chance ?


On 23 May 2016 at 20:48, Bazan, Hernan <hernan.bazan@intel.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


pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: JDBC client hangs on socketRead()
Next
From: Dave Cramer
Date:
Subject: Re: JDBC client hangs on socketRead()