You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/08/14 16:04:00 UTC
[jira] [Commented] (LOG4J2-2911) Log4j2EventListener in
...spring.cloud.config.client listens for wrong event
[ https://issues.apache.org/jira/browse/LOG4J2-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177839#comment-17177839 ]
Ralph Goers commented on LOG4J2-2911:
-------------------------------------
Thanks! You are welcome to submit a PR if you can get to it before I can.
> 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
>
> {{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)