[
https://issues.apache.org/jira/browse/KNOX-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2284:
--------------------------------
Description:
When there is a CM descriptor in the KNOX_DESCRIPTORS_DIR at startup time and
the KNOX descriptors found in this CM descriptor did not exist before then Knox
does not pick up them.
The reason is: the shared-provider/descriptor/topology monitor starts after the
CM descriptor is being parsed and the Knox descriptors are persisted.
Recommended solution: move the CM descriptor handling after the monitors are
started.
was:
When there is a CM descriptor in the KNOX_DESCRIPTORS_DIR at startup time and
the KNOX descriptors found in this CM descriptor did not exist before Knox does
not pick up them.
The reason is: the shared-provider/descriptor/topology monitor starts after the
CM descriptor is being parsed and the Knox descriptors are persisted.
Recommended solution: move the CM descriptor handling after the monitors are
started.
> CM descriptors do not get picked up at Gateway start
> ----------------------------------------------------
>
> Key: KNOX-2284
> URL: https://issues.apache.org/jira/browse/KNOX-2284
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.4.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.4.0
>
>
> When there is a CM descriptor in the KNOX_DESCRIPTORS_DIR at startup time and
> the KNOX descriptors found in this CM descriptor did not exist before then
> Knox does not pick up them.
> The reason is: the shared-provider/descriptor/topology monitor starts after
> the CM descriptor is being parsed and the Knox descriptors are persisted.
> Recommended solution: move the CM descriptor handling after the monitors are
> started.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
