[CONTROLLER-532] logback initialization throws UnknownHostException when host name is not resolvable. Created: 02/Jun/14 Updated: 19/Oct/17 Resolved: 19/May/16 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | adsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Prasanth Pallamreddy | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| External issue ID: | 1127 |
| Description |
|
This issue appears to be fixed in logback/1.0.13. Upgrade logback version to 1.0.13 See http://jira.qos.ch/browse/LOGBACK-749 for details. The following error is seen during logback initialization. 13:18:51,263 |-ERROR in ch.qos.logback.core.util.ContextUtil@73a2efd3 - Failed to get local hostname java.net.UnknownHostException: YYYYYYYYYYYYYYY : nodename nor servname provided, or not known |
| Comments |
| Comment by Carol Sanders [ 04/May/15 ] |
|
This bug is part of the project to Move all ADSAL associated component bugs to ADSAL |
| Comment by Robert Varga [ 19/May/16 ] |
|
Logging is handled by Karaf |