ARTIFACTORY: How to resolve Method Not Yet Implemented errors

AuthorFullName__c
Nir Ovadia
articleNumber
000005358
FirstPublishedDate
2022-08-04T06:29:17Z
lastModifiedDate
2025-05-15

ARTIFACTORY: How to resolve Method Not Yet Implemented errors

If you’re seeing errors like the below on startup that is causing the application to fail:

HikariCP Main - Connection org.postgresql.jdbc.PgConnection@3d9a8e65 marked as broken because of SQLSTATE(0A000), ErrorCode(0) java.sql.SQLFeatureNotSupportedException: Method org.postgresql.jdbc.PgConnection.setNetworkTimeout(Executor, int) is not yet implemented.

This usually happens after upgrades. The issue here is that either a JDBC driver needs to be updated, or the application is resolving an older JDBC driver instead of the newer one.


To check it out, we can go to the

$ARTIFACTORY_HOME/app/artifactory/tomcat/lib/

folder. Here is where the JDBC drivers are stored. Let’s say we’re using a Postgres DB, we should expect to see some sort of postgres.jar in here.
The thing with upgrades is it could cause the wrong jar to get resolved, so if we have an old postgres-9.4.jar and a new postgresql-42.2.25.jar in the file, it could be using the old postgres-9.4.jar which doesn’t have some of the methods the application is trying to run. Even if it was working fine pre-upgrade, on upgrade, it looks at this folder again and tries to guess which one is the right postgres jar. 

To fix this, we can remove any postgres*.jar files we don’t need and only install the Postgres JDBC driver we want. The same can be done with any other DB type as well. Our DB docs should have the link to the Driver download pages (for example ​​https://www.jfrog.com/confluence/display/JFROG/MySQL#MySQL-ConfiguringArtifactorytouseMySQL has a link to https://dev.mysql.com/downloads/connector/j/).
From there a restart will capture the proper JDBC driver and the instance should get past this error.