Unable to deploy - ClassNotFoundException : TalendEndpoint cannot be found

[ETalend_Support1613494335]

Hello,

I'm setting a local runtime installation, and I encountered some issues on deployment.

I am using a Talend 7.3.1 version, using Runtime installation provided by Talend - nothing special.

I created some test route with a cTalendJob, which is sending a message to activeMQ.

I have no issue running the route in studio, neither on building the route, but when I manually deploy the .kar file in /deploy repository, the route's bundles are in failure (more details attached)

I identified that the issue seems to be related to the cTalendJob, maybe some dependencies are missing, but I have no idea how to correct this.

Can you help me ?

Thank you

[Anonymous]

Hello,

is it possible to share your job (route+ ci job) so that we can test in our side?

thanks

Aiming

[ETalend_Support1613494335]

Hello,

Please find attached the route + job

[Anonymous]

Hello,

Thanks for provide the job, but I can't reproduce the issue in my side, the route can be active successfully as the below

it maybe related to the runtime cache data, could you please try the below steps:

1. stop runtime
2. backup the folder runtime/data as a different name
3. clear all the files and folders in runtime/data folder
4. restart runtime

[ETalend_Support1613494335]

The issue seems not resolved, but I have only bundle in failure this time :

 

I think the real issue may be the Talend Studio installation, because I have the same issue when deploying in development environment (which is working fine for 300+ routes)

[Anonymous]

maybe it's related to your runtime installation issue. it's suggested to download a new ESB manually and extract it.

https://www.opensourceetl.net/tis/tdf_731/Talend-ESB-V7.3.1-20200218143610.zip

(you can find the username and password in talend license email)

[ETalend_Support1613494335]

I did try reinstalling both runtime and studio - the problem still persists

[ETalend_Support1613494335 · Accepted solution]

It seems the problem was caused by a difference in version between Talend Studio and Talend Runtime - without any patches, the route is working fine.