Before deploying a new Talend ESB Route or Service it is important to first undeploy the previous version.
Failing to do this can result in multiple versions of the same Talend ESB runtime Route or Service running simultaneously. It is not immediately obvious that this has happened from looking at the Talend Administration Centre (TAC). The ESB Conductor will show only the last deployed version. However, you may realise something is not right when you see for example, more consumers listening to an MQ Queue than expected.
In the example below, example_route version 0.1.0 was deployed in TAC. Afterwards, version 0.2.0 was deployed, but 0.1.0 was not undeployed first.
The steps below will describe how to find what other versions of the Route are running and how to stop / uninstall them.
In ESB Runtime server’s console, navigate to the directory where the Talend ESB Runtime is installed.
Open client (client.bat if its Windows).
The karaf screen if shown.
Listed below are the installed / deployed bundles. Some of these are internal Talend modules.
example_route has version 0.1.0 and version 0.2.0 ‘Active’ (Deployed).
To ‘stop’ version 0.1.0, type ‘bundle:stop [bundle id]’ e.g. bundle:stop 413
Now type bundle:list. example_route version 0.1.0 now has a status of ‘Resolved’.
To ‘uninstall’ version 0.1.0, type ‘bundle:uninstall [bundle id]’ e.g. bundle:uninstall 413
Now type bundle:list. example_route version 0.1.0 now has disappeared from the list.
If you need to ‘start’ a bundle use e.g. ‘bundle:start [bundle id]’ e.g. bundle:start 413
The remaining version, 0.2.0 is now the only version of example_route running on the Talend Runtime.