Chris, At this point I'd write small piece of code to test if the url and failover is working correctly. Sounds like you have a considerably sized stack making it difficult to debug. With a small piece of code it should become clear as to how things work or don't as the case may be
Dave Cramer da...@postgresintl.com www.postgresintl.com On 21 March 2018 at 17:13, Adrian Klaver <adrian.kla...@aklaver.com> wrote: > On 03/21/2018 01:56 PM, chris wrote: > >> I did the re install not to change versions but to now know what version >> I am running >> > > My previous question was not as clear as should have been. > So: > 1) At some place in your software stack there is some sort of > configuration that links your app via JDBC to a Postgres JDBC driver. If > you know where that configuration is you should be able to find the driver > and presumably the version. > 2) So when you say you did a reinstall do you mean you are now pointing > the configuration at postgresql-42.2.1.jre7.jar? FYI > postgresql-42.2.2.jre7.jar is actually the latest: > https://jdbc.postgresql.org/download.html > > > >> >> On 03/21/2018 02:44 PM, Adrian Klaver wrote: >> >>> On 03/21/2018 01:16 PM, chris wrote: >>> >>>> I wasnt able to find what version we had installed so we went ahead and >>>> reinstalled it >>>> >>> >>> Maybe I am missing something, but if you could not find the version you >>> where using how do you know installing a new driver actually changed the >>> version you are using now? >>> >>> >>> >>>> we downloaded the current version JDBC 4.1 Driver 42.2.1.jre7 >>>> >>>> >>>> We are still having the same problem. >>>> >>>> Thanks >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> > > -- > Adrian Klaver > adrian.kla...@aklaver.com > >
