Five Stars

Deploying a karaf file restarts all the bundles

Hello

One strange thing : when we deploy a new kar file into karaf (either by dropping it in the /container/deploy directory, or in the console lanching "kar:install file:/....), the other bundles that already run in Karaf all change their statuses to "stopped" then "resolved" then "active".

 

Thus there is a service interrupt that cannot be acceptable on production systems.

A Talend partner told me this is not intented behaviour, but he could not say why this happens.

 

the .kar files contain routes developped with Talend ESB Studio.

 

Would could be the reason ?

Thank you

Loko

6 REPLIES
Moderator

Re: Deploying a karaf file restarts all the bundles

Hello Loko,

We have redirected your issue to our ESB expert and will keep you posted.

Could you please indicate on which build version you got it?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars

Re: Deploying a karaf file restarts all the bundles

Hello Sabrina

 

We use Talend ESB 6.3.0

The .../container/versions.txt file says "6.3.1_SE_206_release/6.3.1", and when connecting to Karaf console it says "Apache Karaf (4.0.7)".

Best,
Loko

Employee

Re: Deploying a karaf file restarts all the bundles

Hi Loko,

 

In order to identify the root cause of this kind of "bundle refresh" problem, you need to looking into the details of Runtime/logs/tesb.log, especially the "Refreshing bundles:" information, that indicate e.g. bundle A is refreshing because wired to bundle B which is being refresh ... Basically, if some optional Import-packages of the bundle are satisfied then it will be refreshed.

 

Does your route has cMap or cMQConnectionFactory components involved? There are few jira issues the "bundle refresh" happening sometimes in this case.

 

Regards.

Xilai

Five Stars

Re: Deploying a karaf file restarts all the bundles

Hi Xilai

 

Yes some routes contain cMQConnectionFactory components, and yes tesb.log shows some bundle wires :

 

2017-10-12 09:15:52,287 | Refreshing bundles:
2017-10-12 09:15:52,287 |     activemq-karaf/5.14.1 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R7_PU017B_BP_FROMKHEOPSTOSAP/0.1.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R_BROKER_BUS/0.1.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R_BROKER_KHEOPS/0.1.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R_BROKER_KYRIBA/0.1.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R_BROKER_NOTILUS/0.1.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R_BROKER_OLGA/0.1.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R_BROKER_PIM/0.2.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)
2017-10-12 09:15:52,287 |     gfc.R_BROKER_SAP/0.1.0 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is 
...
Employee

Re: Deploying a karaf file restarts all the bundles

Five Stars

Re: Deploying a karaf file restarts all the bundles

Hello Xldai

Thank you for your advice. We tried the actions in the other issue, but it had no effect.
When you say "emove the activemq feature from the kar feature.xml also an option", you mean we should unzip the kar file, modify its feature.xml , zip it again then put it again in the deploy directory, that's right ?