|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
10/Jun/08 08:40 AM
|
|
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.
|
|
Description
|
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. |
Show » |
made changes - 06/Jun/08 01:49 PM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
In Progress
[ 3
]
|
made changes - 10/Jun/08 08:40 AM
|
Resolution
|
|
Fixed
[ 1
]
|
|
Status
|
In Progress
[ 3
]
|
Closed
[ 6
]
|
|
Bug
Closed
Major
Reactivation of a component after a configuration update should be completely asynchronous
