Multiple MySQL version issue. Communications link failure.

[ABin_Abdul_Rahim1632280426]

In my job I have 2 tDBInput.

tDBInput_1 is using MySQL 5, and tdBInput_2 is using MySQL 8.

When I try to run this job in Remote Engine, it will lead to error.

If I disabled one of the tDBInput, the job can be execute successfully.

Please advice, how can I resolve this issue.

[Anonymous]

Can you share some more detail please? Are you using connection components or connecting with each component (input/ouput components)? Does the job run in the Studio? Can you share the error you get?

[ABin_Abdul_Rahim1632280426]

I don't use any connection components.

I just using tDBInput and tLogRow to extract the results.

And the property type for tDBInput is repository.

This can be run on studio, however failed to run on remote engine through TMC.

Below are the error log of the particular job.

Task 61a9cbe6851ee7246e92c8da/4.5 failed unexpectedly.

org.talend.ipaas.rt.flow.controller.impl.FlowExecutionException: Step 6fbae07f-714c-4eb7-9367-47f0f1c219ee failed with code 1 and error Job stopped with errors or unable to run. Exception in component tDBInput_1 (test_connection) com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

    at org.talend.ipaas.rt.flow.controller.impl.JobControllerImpl.doRun(JobControllerImpl.java:167) ~[?:?]

    at org.talend.ipaas.rt.flow.controller.impl.AbstractControllerImpl.lambda$run$0(AbstractControllerImpl.java:107) ~[?:?]

    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_292]

Caused by: java.lang.Exception: Job stopped with errors or unable to run. Exception in component tDBInput_1 (test_connection) com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

[Anonymous]

If you remove the MySQL 5 components, it will work with MySQL 8. If you remove the MySQL 8 components, it will work with MySQL 5. Is that correct?

[ABin_Abdul_Rahim1632280426]

Yes, that is correct.

[Anonymous]

OK, this sounds like it could potentially be a library issue within the remote engine. It would be very difficult to identify this without actually having a look myself. Since you are using a Remote Engine, you should have a support license. I think the best thing for you to do is to raise a support call so that they can take a deeper look into this for you.