[
https://issues.apache.org/jira/browse/LOG4J2-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497594#comment-14497594
]
Thiago Kronig commented on LOG4J2-996:
--------------------------------------
Not sure if this failure is really a bug.
Anyway, the stacktrace is:
{{java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
at
org.apache.logging.log4j.core.appender.ConsoleAppender.getOutputStream(ConsoleAppender.java:200)
at
org.apache.logging.log4j.core.appender.ConsoleAppender.getManager(ConsoleAppender.java:177)
at
org.apache.logging.log4j.core.appender.ConsoleAppender.createDefaultAppenderForLayout(ConsoleAppender.java:108)
at
org.apache.logging.log4j.core.config.DefaultConfiguration.<init>(DefaultConfiguration.java:62)
at
org.apache.logging.log4j.core.LoggerContext.<init>(LoggerContext.java:70)
at
org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoaderContextSelector.java:145)
at
org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:70)
at
org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:57)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:142)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:175)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:102)
at
org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
at
org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:277)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:288)
at Log4j2WindowsBug.main(Log4j2WindowsBug.java:11)
Caused by:
at
org.fusesource.jansi.WindowsAnsiOutputStream.getConsoleInfo(WindowsAnsiOutputStream.java:104)
at
org.fusesource.jansi.WindowsAnsiOutputStream.<init>(WindowsAnsiOutputStream.java:97)
... 22 more}}
> ConsoleAppender fails to load Jansi in Windows 8.1 x64
> ------------------------------------------------------
>
> Key: LOG4J2-996
> URL: https://issues.apache.org/jira/browse/LOG4J2-996
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.2
> Environment: Windows 8.1 x64
> Reporter: Thiago Kronig
> Priority: Minor
> Labels: jansi
> Fix For: 2.3
>
>
> ConsoleAppender tries to construct a
> org.fusesource.jansi.WindowsAnsiOutputStream by calling its constructor via
> reflection, which throws IOException after a JNI call to
> GetConsoleScreenBufferInfo, forcing ConsoleAppender to ignore Jansi.
> This happens on Windows 8.1 x64.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
