[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
moritz löser updated LOG4J2-905:
--------------------------------
Description:
(see
[here|http://stackoverflow.com/questions/27103400/log4j2-how-to-disable-date-lookup-log4j-throws-exception]
for some details )
At the moment it is not possible to log stuff like this:
{noformat}
log.info("${date:now:buhu}");
{noformat}
("ERROR Invalid date format: "now:yyyyMMdd-HHmmss", using default
java.lang.IllegalArgumentException: Illegal pattern character 'n'")
Because log4j2 tries to change the logged output - want to substitute a date.
This is intransparently limiting the logging.
nobody knows what kind of strings are allowed and what kind of strings will be
interpreted by log4j2. But it becomes worse if you use slf4j and switch the
logger implementation to log4j2 - it could happen that just switching breaks
your code.
This is a *real issue* if you use libraries like *apache camel* because camel
itself uses strings like ${date:now:YYYY...} to substitute stuff like file
names. see http://camel.apache.org/simple.html
At the moment camel is locking this stuff on debug (sometime i need it to see
if i correctly set up camel) so it is no production issue here. But what about
other libraries or the future?
The only way i see is a switch to disable all kinds of lookups and it should
probably off by default.
was:
(see
[here|http://stackoverflow.com/questions/27103400/log4j2-how-to-disable-date-lookup-log4j-throws-exception]
for some details )
At the moment it is not possible to log stuff like this:
log.info("${date:now:buhu}"); ("ERROR Invalid date format:
"now:yyyyMMdd-HHmmss", using default java.lang.IllegalArgumentExcepti
on: Illegal pattern character 'n'")
Because log4j2 tries to change the logged output - want to substitute a date.
This is intransparently limiting the logging.
nobody knows what kind of strings are allowed and what kind of strings will be
interpreted by log4j2. But it becomes worse if you use slf4j and switch the
logger implementation to log4j2 - it could happen that just switching breaks
your code.
This is a *real issue* if you use libraries like *apache camel* because camel
itself uses strings like ${date:now:YYYY...} to substitute stuff like file
names. see http://camel.apache.org/simple.html
At the moment camel is locking this stuff on debug (sometime i need it to see
if i correctly set up camel) so it is no production issue here. But what about
other libraries or the future?
The only way i see is a switch to disable all kinds of lookups and it should
probably off by default.
> Ability to disable (date) lookup completely, compatibility issues with other
> libraries like camel
> -------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-905
> URL: https://issues.apache.org/jira/browse/LOG4J2-905
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: moritz löser
> Labels: date, lookup
>
> (see
> [here|http://stackoverflow.com/questions/27103400/log4j2-how-to-disable-date-lookup-log4j-throws-exception]
> for some details )
> At the moment it is not possible to log stuff like this:
> {noformat}
> log.info("${date:now:buhu}");
> {noformat}
> ("ERROR Invalid date format: "now:yyyyMMdd-HHmmss", using default
> java.lang.IllegalArgumentException: Illegal pattern character 'n'")
> Because log4j2 tries to change the logged output - want to substitute a date.
> This is intransparently limiting the logging.
> nobody knows what kind of strings are allowed and what kind of strings will
> be interpreted by log4j2. But it becomes worse if you use slf4j and switch
> the logger implementation to log4j2 - it could happen that just switching
> breaks your code.
> This is a *real issue* if you use libraries like *apache camel* because camel
> itself uses strings like ${date:now:YYYY...} to substitute stuff like file
> names. see http://camel.apache.org/simple.html
> At the moment camel is locking this stuff on debug (sometime i need it to see
> if i correctly set up camel) so it is no production issue here. But what
> about other libraries or the future?
> The only way i see is a switch to disable all kinds of lookups and it should
> probably off by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
