[jira] [Resolved] (KAFKA-2688) Avoid forcing reload of `Configuration`

["Ismael Juma (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma resolved KAFKA-2688.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.9.1.0)
                   0.9.0.0

This was actually fixed by a commit from [~rsivaram].

> Avoid forcing reload of `Configuration`
> ---------------------------------------
>
>                 Key: KAFKA-2688
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2688
>             Project: Kafka
>          Issue Type: Bug
>          Components: security
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>            Priority: Critical
>             Fix For: 0.9.0.0
>
>
> We currently call `Configuration.setConfiguration(null)` from a couple of places in our codebase (`Login` and `JaasUtils`) to force `Configuration` to be reloaded. If this code is removed, some tests can fail depending on the test execution order.
> Ideally we would not need to call `setConfiguration(null)` outside of tests. Investigate if this is possible. If not, we should at least ensure that reloads are done in a safe way within our codebase (perhaps using a lock).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)