topic ESB Runtime Deployment 7.2.1 - net.sourceforge.jtds.jdbc.Driver cannot be found in Talend Studio

ESB Runtime Deployment 7.2.1 - net.sourceforge.jtds.jdbc.Driver cannot be found

nmodi — Sat, 16 Nov 2024 02:54:25 GMT

I have migrated my jobs from tlaend 6.4.1 to 7.2.1
and getting this error when I deploy ESB job with tRESTRequest component,

it works localy fine & build fine without any error,

however getting this error when I deploy this as server on my runtime server

net.sourceforge.jtds.jdbc.Driver cannot be found by pii_internal.ESB_SalesTax_2.4.0
java.lang.ClassNotFoundException: net.sourceforge.jtds.jdbc.Driver cannot be found by pii_internal.ESB_SalesTax_2.4.0

I compared build package from 6.4.1 to 7.2.1 & I see that jtds-1.3.1.jar was always part of build package for every job, it doesn't need to be installed separately on the server however something has changed in 7.2.1 version that it is not taking jtds-1.3.1.jar as part of build package.

Could you please help?

Re: ESB Runtime Deployment 7.2.1 - net.sourceforge.jtds.jdbc.Driver cannot be found

nmodi — Mon, 23 Mar 2020 21:38:54 GMT

I got an update from talend support that I should use ms sql jdbc instead open source jtds & it worked for me.

however that require us to change all of our ESB jobs to use ms sql jdbc driver & that is tedious job as part of this migration. looking for other recommendation that doesn't require us to change the job.

Re: ESB Runtime Deployment 7.2.1 - net.sourceforge.jtds.jdbc.Driver cannot be found

FrancoisSmfy — Wed, 27 May 2020 14:41:03 GMT

The support gives me this solution :

Close the Studio
Open the studio installation folder, and go to “studio\plugins”
Fin the file “org.talend.repository_X.X.X.AAAMMDD_XXXX.jar”
Open it as an archive (with 7Zip or other), and extract the "ressources/osgi-exclude.properties” file to "studio\esb”
Edit the “studio\esb\osgi-exclude.properties” file
Comment the line with "jtds"
Save and close
Restart the Studio

This file specifiy the libraries to exclude when we publish in OSGI. When it's here, it's loaded instead of the one in the .jar file