I noticed a wierd behaviour. I deployed the 1st version of route. Later we had to update the route with some enhancement. Nexus artifact is getting updated (timestamp changed). In ESB conductor , new contexts are getting reflected, but I think due to cache issues, ESB conductor is still pointing to the old code. I made sure that the feature is not present in the Karaf. I tried the commands feature:repo-remove , feature:uninstall etc.The same code is working fine in studio. But when deployed to TAC ESB Conductor , I think it is pointing to old code. Has anyone faced this issue, If so, what is the solution ?
Thanks for the reply JGM. I published it from Talend Studio. CICD deployment is not working for ESB routes in Talend 6.4. So should we publish from Publisher in TAC. Came to know that Publisher is no more available in higher versions of Talend.
We deleted the data directory and restarted the runtime services. Even then the same issue.
Could you please tell me the path where directories needs to be deleted? Is it talend/runtime/etc/job_name.cfg?
@talendfolks, this fix can be done in Dev but not in prod. Do you have any idea why this issue caused and what is the best fix for this?
Just ran into this issue deploying to my Integration environment with Talend Data Services Platform 6.4.1. I'm using Karaf directly and even tried deleting the data folder - it didn't update anything - I'm still getting old values for default contexts (previous configs were deleted before shutting down Karaf to delete the data folder).
Hope this stuff is fixed in version 7.
With your subscription solution, could you please create a case on talend support portal so that we could give you a remote assistance to see if it is a bug?
Introduction to Talend Open Studio for Data Integration.
Practical steps to developing your data integration strategy.
Create systems and workflow to manage clean data ingestion and data transformation.