Details
-
Type: Bug
-
Status: Closed
-
Priority: Blocker
-
Resolution: Fixed
-
Affects Version/s: 2.11.1.7
-
Component/s: Command Line Interface, Dev and Dep
-
Labels:None
-
Environment:Best seen using shadowJar on command line.
-
Urgency:Urgent
Description
Since upgrading to log4j 2.16 and then 2.17, using the log4j 1 compatibility bridge for minimal re-coding, most/all Cache.log messaging is coming out on stderr, and only as (presumably the default template):
%d [%thread] %-5level %logger - %msg%n
It appears that INFO messages are appearing on the command line and in the Java Console, but DEBUG (or other) log levels are appearing as the template on STDERR and not at all in the Java Console.
%d [%thread] %-5level %logger - %msg%n
It appears that INFO messages are appearing on the command line and in the Java Console, but DEBUG (or other) log levels are appearing as the template on STDERR and not at all in the Java Console.
Attachments
Issue Links
- related with
-
JAL-3933 Use of log4j and mitigation of critical alert "Apache Log4j 2 vulnerability (CVE-2021-44228)"
- Closed
-
JAL-3934 Jalview 2.11.1.6 release for CVE-2021-45105 Update log4j2 to 2.17.0
- Closed
-
JAL-3137 Support HiDPI scaling for hi-resolution displays
- Open
-
JAL-3953 Update java2script bindings for log4j2 for JalviewJS
- Closed