Github user jcetkov commented on the issue:
https://github.com/apache/logging-log4j2/pull/29
@mikaelstaldal I'm not able to reproduce as I'm not running windows - I've
seen it in stacktrace from another user where the (TomEE) startup died with the
following error
```
java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no
jansi64-1.8 in java.library.path, no jansi-1.8 in java.library.path, no jansi
in java.library.path, Native Library
C:\Users\user\AppData\Local\Temp\jansi-64-1.8.dll already loaded in another
classloader]
at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:184)
at org.fusesource.hawtjni.runtime.Library.load(Library.java:142)
at org.fusesource.jansi.internal.Kernel32.<clinit>(Kernel32.java:37)
at
org.fusesource.jansi.WindowsAnsiOutputStream.<clinit>(WindowsAnsiOutputStream.java:52)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
