You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Aaron Lindsey (Jira)" <ji...@apache.org> on 2019/08/20 23:46:00 UTC
[jira] [Commented] (GEODE-3689) Unable to specify custom log4j
configuration file from gfsh
[ https://issues.apache.org/jira/browse/GEODE-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911821#comment-16911821 ]
Aaron Lindsey commented on GEODE-3689:
--------------------------------------
[~klund] does the work around splitting out log4j-core into a submodule fix this issue?
> Unable to specify custom log4j configuration file from gfsh
> -----------------------------------------------------------
>
> Key: GEODE-3689
> URL: https://issues.apache.org/jira/browse/GEODE-3689
> Project: Geode
> Issue Type: Bug
> Components: gfsh, logging
> Reporter: Jens Deppe
> Assignee: Kirk Lund
> Priority: Major
>
> When starting a server with gfsh, it does not honor a log4j configuration location by specifying {{--J=-Dlog4j.configurationFile=/path/to/log4j2.xml}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)