ESB Route Deployment Issue

[ALoth]

Hi,

Our platform based on Talend 8.0.1.20211109_1610.

We have developed generic routes. These routes need to be deployed multiple times with different contexts. A context corresponds to a use case.

The operation of these routes is relatively simple.

• Retrieving a file from an FTP --> feeding an ActiveMQ queue
• Retrieving a message from an ActiveMQ queue --> Writing the content to an SFTP

Everything works on dev and work on prod.

If we deploy a route and keep its default Property ID (PID) and choose a context, it works.

cf img1

However, if we deploy a route and define its Property ID (PID) (because we plan to deploy the same route multiple times with different contexts), the route starts with the default context (and not the chosen context).

cf img2

To me,

• this is a bug
• or we are missing a step to properly deploy the same route with different contexts.

Can you help us resolve this issue, specifically deploying the same route multiple times with different contexts?

Regards,

[anselmopeixoto]

Hello @Aurélien Loth​ 

Can you try to refresh the bundle using karaf console (Talend Runtime)?

You'll need to get the bundle id using list command, and then you can execute "refresh 123".

[ALoth]

Hi,

thanks for your help.

I have reset everything.

I started by adding my route with a predefined context.

 

In the logs, the deployment goes well,

07:20:28.878 INFO [RMI TCP Connection(26565)-192.168.102.9] Adding features: testContext-feature/[0.26.0,0.26.0]

07:20:42.074 INFO [features-2-thread-1] Changes to perform:

07:20:42.074 INFO [features-2-thread-1]  Region: root

07:20:42.075 INFO [features-2-thread-1]   Bundles to install:

07:20:42.075 INFO [features-2-thread-1]    mvn:com.chronodrive.exchangeplatform.route/testContext/0.26.0

07:20:42.075 INFO [features-2-thread-1]    mvn:org.eclipse.jetty.websocket/websocket-common/9.4.38.v20210224

07:20:42.076 INFO [features-2-thread-1] Installing bundles:

07:20:42.076 INFO [features-2-thread-1]  mvn:com.chronodrive.exchangeplatform.route/testContext/0.26.0

07:20:42.105 INFO [features-2-thread-1]  mvn:org.eclipse.jetty.websocket/websocket-common/9.4.38.v20210224

07:20:42.147 INFO [features-2-thread-1] Starting bundles:

07:20:42.147 INFO [features-2-thread-1]  exchange_platform.testContext/0.26.0

07:20:42.747 INFO [features-2-thread-1] The property placeholder processor for $core1{, } in bundle exchange_platform.testContext/0.26.0 found an immutable Constructor Argument at location Bean named jmxEventNotifier->Argument index -1 and value type null->. This may prevent properties, beans, or other items referenced by this component from being properly processed.

07:20:42.748 INFO [features-2-thread-1] The property placeholder processor for $core1{, } in bundle exchange_platform.testContext/0.26.0 found an immutable Factory Component at location Bean named jmxEventNotifier->. This may prevent properties, beans, or other items referenced by this component from being properly processed.

07:20:55.002 INFO [features-2-thread-1] Using custom LifecycleStrategy with id: LifecycleStrategy0 and implementation: org.talend.esb.servicelocator.cxf.internal.LocatorLifecycleStrategy@127debbe

07:20:55.391 INFO [features-2-thread-1] Blueprint bundle exchange_platform.testContext/0.26.0 has been started

07:20:55.392 INFO [Blueprint Event Dispatcher: 1] Attempting to start CamelContext: exchange_platform.testcontext_0_26.testContext

07:20:55.735 INFO [Blueprint Event Dispatcher: 1] JMX is enabled

07:20:55.935 INFO [Blueprint Event Dispatcher: 1] Backlog Tracing is enabled on CamelContext: exchange_platform.testcontext_0_26.testContext

07:20:55.967 INFO [Blueprint Event Dispatcher: 1] Routes startup summary (total:1 started:1)

07:20:55.968 INFO [Blueprint Event Dispatcher: 1]   Started testContext_cDirect_3 (direct://unexpected_error)

07:20:55.968 INFO [Blueprint Event Dispatcher: 1] Apache Camel 3.11.1.tesb1 (exchange_platform.testcontext_0_26.testContext) started in 12s825ms (build:12s249ms init:543ms start:33ms)

07:20:55.971 INFO [features-2-thread-1] Done.

and during execution, I see in the logs that it did not take the defined context but rather the default context.

INFO  | jvm 1  | 2023/10/24 07:20:27 | 07:20:27.474 [features-2-thread-1] ERROR exchange_platform.testcontext_0_26.testContext - Retreiving Default

If I do a bundle:list, I find my route, but its name does not match what I defined.

503 │ Active  │ 80 │ 0.26.0    │ testContext

If I refresh the bundle, there is no change.

[ALoth]

Hello,

anyone can help us with our problem ? 🙂

Regards,

[jeoste]

Hello,

I encountered a similar problem, not sure if it can helps, but the workaround is to deploy each route with only one context inside and deploy X times the route (X corresponds to the number of environment you have).

Regards