[logback-dev] [JIRA] (LOGBACK-1370) groovy-based configuration tries to resolve the hostname eagerly, failing in environments with no hostname
QOS.CH (JIRA)
noreply-jira at qos.ch
Fri Jan 12 19:42:00 CET 2018
Kirill Morozov created LOGBACK-1370:
---------------------------------------
Summary: groovy-based configuration tries to resolve the hostname eagerly, failing in environments with no hostname
Key: LOGBACK-1370
URL: https://jira.qos.ch/browse/LOGBACK-1370
Project: logback
Issue Type: Bug
Components: logback-classic
Affects Versions: 1.2.3
Environment: Aws Lambda
Reporter: Kirill Morozov
Assignee: Logback dev list
When configuring logback via a logback.groovy, the first thing that the GafferConfigurator does is call {{binding.setProperty("hostname", ContextUtil.localHostName);}}.
In a serverless environment, such as AWS Lambda, this fails with a UnknownHostException. As I understand it Lambdas don't have hostnames as they can't be addressed from the internet.
We should either wrap this line in a try/catch or move the hostname resolution to where it is used.
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
More information about the logback-dev
mailing list