You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "pengliang (JIRA)" <ji...@apache.org> on 2019/06/05 03:00:01 UTC

[jira] [Assigned] (SCB-1297) Print warn log about config resolving failure while fetching config from Spring Environment

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

pengliang reassigned SCB-1297:
------------------------------

    Assignee: pengliang  (was: YaoHaishi)

> Print warn log about config resolving failure while fetching config from Spring Environment
> -------------------------------------------------------------------------------------------
>
>                 Key: SCB-1297
>                 URL: https://issues.apache.org/jira/browse/SCB-1297
>             Project: Apache ServiceComb
>          Issue Type: Improvement
>          Components: Java-Chassis
>    Affects Versions: java-chassis-1.2.1
>            Reporter: YaoHaishi
>            Assignee: pengliang
>            Priority: Major
>
> Currently the ConfigurationSpringInitializer is deployed to get the Environment from Spring. All of the config items in the Environment are fetched with the value resolved from the Environment. These config items are later inject into the configurations of ServiceComb-Java-Chassis.
> If there are some environment items with irregular value, the Spring Environment may fail to resolve the config item and throw an Exception, even though that environment items are not relative to the microservice instances.
> It's necessary to provide a switch to disable the Exception in this situation. If users don't want the boot up process to be interrupted by such failure, they can enable the suppression feature, then all of such Exceptions are caught and only warn logs are printed to show which config keys are failed to be resolved.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)