cancel
Showing results for 
Search instead for 
Did you mean: 

Reloaded components are not started

Juha_Kilpi
Champ on-the-rise
Champ on-the-rise

When components get reloaded they will stay in activated state and will not get started.

The problem seems to be in ComponentManagerImpl.applyStashWhenRunning () where new components are activated in one loop, and then in the next "isStandby()" loop when new components should be added to standby list, components are already in activated state instead of resolved, so they will not be added to the list.

Because components are not added to the standby list, they will not be started when resumed.

// activate the new components
for (RegistrationInfo ri : stash.toAdd) {
    if (ri.isResolved()) {
        activateComponent(ri);
    }
}
if (isStandby()) {
    // activate the new components
    for (RegistrationInfo ri : stash.toAdd) {
        if (ri.isResolved()) {
            activateComponent(ri);
            // add new components to standby list
            this.standby.add(ri);
        }
    }
}
1 ACCEPTED ANSWER

Kevin_Leturc
Star Contributor
Star Contributor

Hello,

Thanks for reporting this issue.

I created NXP-25318 to fix it.

Thanks

View answer in original post

2 REPLIES 2

Kevin_Leturc
Star Contributor
Star Contributor

Hello,

Thanks for reporting this issue.

I created NXP-25318 to fix it.

Thanks

Thank you for looking into this.