Forum Discussion

brianm's avatar
brianm
New Contributor II
12 months ago
Solved

Jar file download failed : NOT FOUND

Greetings.

I'm attempting to perform some operations against a MySQL 8.0.33 server. I created a SnapLogic MySQL database  account, and uploaded mysql-connector-j-8.0.33.jar to the JDBC driver property of the account configuration popup. Pressing the validate button shows a positive result. I can also confirm a valid connection from the MySQL side.

However, when I use this connection in a MySQL Execute snap, I receive an error: "com.snaplogic.api.ExecutionException: Jar file download failed : NOT FOUND."

There are no network obstructions. The username/password is absolutely correct and validated by multiple means.

Any ideas?

  • brianm's avatar
    brianm
    12 months ago

    Yes, I experienced the same behavior.

    When running a pipeline, the default action is to look for jar files directly in the project space, even if you selected an alternate location in the GUI when creating and validating the account. In my case, I have the jar file in a shared project space. The fix, it seems, is to provide the full path to the jar file in the account JDBC driver attribute. In my case, it looked like this:

    ProductionInstance/IdentityManagement/shared/mysql-connector-j-8.0.33.jar

    Hope this helps.

6 Replies

  • svatada's avatar
    svatada
    Former Employee
    12 months ago

    brianmDid you browse to the driver jar location from the snap property, or did you copy and pasted the file name directly into the account configurations?

    • brianm's avatar
      brianm
      New Contributor II
      12 months ago

      I browsed and uploaded from the snap property a few times. I also tried copy/paste. Same result either way.

  • joel_bourgault's avatar
    joel_bourgault
    New Contributor III
    12 months ago

    Same issue here, with some interesting timeline:

    • We want to connect to our MariaDB Maxscale database load balancer, using cyphered connection. This seems to require the Connector J, so we upload it, select it as JDBC JAR, provide the credentials, Validate the connection: all goes well.
    • But then, pipeline fails, with following indication: "failure=Jar file download failed : NOT FOUND".

    Now, the weird part:

    • Coming back to Account, I remove the custom JAR line; now *validation still works* (when it didn't previously without the custome JAR file.)
    • And the pipeline do not fail anymore!

    I will open a support ticket on this; brianm do you experience the same behavior?

    • brianm's avatar
      brianm
      New Contributor II
      12 months ago

      Yes, I experienced the same behavior.

      When running a pipeline, the default action is to look for jar files directly in the project space, even if you selected an alternate location in the GUI when creating and validating the account. In my case, I have the jar file in a shared project space. The fix, it seems, is to provide the full path to the jar file in the account JDBC driver attribute. In my case, it looked like this:

      ProductionInstance/IdentityManagement/shared/mysql-connector-j-8.0.33.jar

      Hope this helps.

      • joel_bourgault's avatar
        joel_bourgault
        New Contributor III
        12 months ago

        Thanks for the reply!

        I just received the same answer from SnapLogic support, and it works indeed: "use the absolute path", as shown in sldb file browser, and not the shortened, relative path.

        As this is an unexpected behavior, I suggested that 1) path entered in file selection is either absolute, or is resolved from Account location, not calling pipeline location, 2) an entry be added to the troubleshooting section. Hope at least one of these will be performed, preferably the first one 😁