Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
nmodi
Creator
Creator

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

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

 

0683p000009M9Ye.png

 

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?

Labels (3)
2 Replies
nmodi
Creator
Creator
Author

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.

FrancoisSmfy
Contributor III
Contributor III

The support gives me this solution :

  1. Close the Studio
  2. Open the studio installation folder, and go to “studio\plugins”
  3. Fin the file “org.talend.repository_X.X.X.AAAMMDD_XXXX.jar”
  4. Open it as an archive (with 7Zip or other), and extract the "ressources/osgi-exclude.properties” file to "studio\esb”
  5. Edit the “studio\esb\osgi-exclude.properties” file
  6. Comment the line with "jtds"
  7. Save and close
  8. 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