Issue Details (XML | Word | Printable)

Key: FELIX-601
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Felix Meschberger
Reporter: Felix Meschberger
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Felix

Reactivation of a component after a configuration update should be completely asynchronous

Created: 06/Jun/08 01:49 PM   Updated: 10/Jun/08 08:40 AM
Return to search
Component/s: Declarative Services (SCR)
Affects Version/s: scr-1.0.2
Fix Version/s: scr-1.0.2

Time Tracking:
Not Specified

Resolution Date: 10/Jun/08 08:40 AM


 Description  « Hide
Currently the component is taken down immediately upon receiving new configuration. This may create issues when components are currently being activated. Therefore the cycling of the component after receiving configuration is to be scheduled for asynchronous execution.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.

Powered by a free Atlassian JIRA open source license for Apache Software Foundation. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators