[
https://issues.apache.org/jira/browse/LOG4J2-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216481#comment-17216481
]
ASF subversion and git services commented on LOG4J2-2911:
---------------------------------------------------------
Commit 8e4eb7a193a5481799a58ffe2ef88d7787fdfb3d in logging-log4j2's branch
refs/heads/master from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=8e4eb7a ]
LOG4J2-2911 - Log4j2EventListener in spring.cloud.config.client listens for
wrong event.
> Log4j2EventListener in ...spring.cloud.config.client listens for wrong event
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-2911
> URL: https://issues.apache.org/jira/browse/LOG4J2-2911
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Spencer Gibb
> Priority: Major
> Fix For: 2.14.0
>
>
> {{org.apache.logging.log4j.spring.cloud.config.client.Log4j2EventListener}}
> currently listens for {{RemoteApplicationEvent}}. This is incorrenct.
> {{RemoteApplicationEvent}} could be any number of things, not just an event.
> Also, refresh events can come from more than spring cloud bus.
> When a remote refresh event is received, an {{EnvironmentChangeEvent}} (which
> is a spring {{ApplicationEvent}}) is published. That would be more
> appropriate to listen for.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
