Jitterbit · Private agents
No suitable driver found
Short answer
This Jitterbit error means the JDBC driver the connection needs is not installed on the private agent. Register the driver in JdbcDrivers.conf and copy its .jar file to JITTERBIT_HOME/tomcat/drivers/lib/.
VerifiedLast verified
01Error text
No suitable driver found for jdbc:<subprotocol>://...02Likely causes
- Jitterbit does not ship with all JDBC drivers, so the required driver must be installed manually.
03How to fix it
- Register the driver in
JdbcDrivers.confand copy its .jar file toJITTERBIT_HOME/tomcat/drivers/lib/. - Restart the agent.
04Official documentation
→Related errors
- Agent Not Running or UnreachableThis Jitterbit Studio message means the private agent services are not running or the agent host cannot reach the Harmony cloud. If the services are not running, start them. If a start fails, check the agent logs.
- Agent is incapable to process this messageThis Jitterbit ProcessEngine.log message means the agent has no free capacity, because every worker thread is in use or a capability metric reached its threshold. Review ProcessEngine.log for repeated capability status changes.
- Failed to find file in the local file storeThis Jitterbit transformation error means deployment metadata for a file did not fully sync from Harmony to the agent, which is usually transient. Re-run the operation. On agent 11.38 and later the metadata is restored on the next environment sync.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries