Hello James, Would it also resolve https://issues.redhat.com/browse/WFCORE-6350 issue? I'm asking because JDK 21 will enter Rampdown Phase One next week on Thursday, 8 June. If the problem is in the JDK then we should report the problem to OpenJDK as soon as possible. Rio On Wed, May 17, 2023 at 6:21 PM James Perkins <jperkins(a)redhat.com&gt; wrote: > Hello All, > I've talked about this many times, but I think it's really the time to > tackle this now. I would like to propose that we remove the boot logging > configuration file and collect log messages until the logging subsystem is > activated. > > This should solve several old JIRA's. Here are 5 of them without looking > too hard :) > > - https://issues.redhat.com/browse/WFCORE-152 > - https://issues.redhat.com/browse/WFCORE-157 > - https://issues.redhat.com/browse/WFCORE-474 > - https://issues.redhat.com/browse/WFCORE-2516 > - https://issues.redhat.com/browse/WFCORE-5275 > > We also benefit from being able to make WildFly much easier to move > between hosts. I see this as a benefit for both bare-metal and cloud. > Currently, once booted the logging.properties is written with absolute > paths which causes boot issues if the file system is changed. > > This would also allow us to upgrade the JBoss Log Manager to the latest > version which includes some nice enhancements. One of which is better > coloring of log messages. We could even log a WildFly logo on boot :) More > seriously though, it will keep WildFy in line with the version that other > projects are using. > > Really, overall, there are nothing but benefits in doing this. The only > cons I see are the following; > > - Potentiel for OOME if all logging is enabled for all loggers. > - This would be extremely rare I would think and may never even > happen. > - A system property would need to be used to define the lowest > logging level wanted. However, this is better than requiring a > logging.properties to control this IMO. > > This change would not remove the ability to use a logging.properties if > the user has chosen to remove the logging subsystem. In those cases, the > logging.properties would still work. However, if the logging subsystem is > also present it would override anything in the logging.properties > configuration. > > Any questions, opinions or comments are welcome. If this seems reasonable > it seems like something we should get moving on ASAP. > > -- > James R. Perkins > JBoss by Red Hat > _______________________________________________ > wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org > To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s