> On Oct 23, 2024, at 09:42, Joey Cochran <joey.coch...@mtsu.edu> wrote: > > Can those be accessLogValve based as well, if so please share how.
Not without modifications or using your own custom valve. From the AccessLogValve documentation: This Valve uses self-contained logic to write its log files, which can be automatically rolled over at midnight each day. (The essential requirement for access logging is to handle a large continuous stream of data with low overhead. This Valve does not use Apache Commons Logging, thus avoiding additional overhead and potentially complex configuration). You should be able to use something like tail to echo the access log file to a terminal window. - Chuck > > From: Chuck Caldarale <n82...@gmail.com> > Sent: Tuesday, October 22, 2024 9:34 PM > To: Tomcat Users List <users@tomcat.apache.org> > Subject: [EXTERNAL] Re: Tomcat stderr/stdout to console > > > > On Oct 22, 2024, at 19:19, Amit Pande <amit.pa...@veritas.com.INVALID> > > wrote: > > > > Hello all, > > > > I am looking for way to print certain logs from Tomcat to actual console > > (stdout) instead of getting those redirected to Catalina.out (default). > > > > e.g. messages like below (and errors failed to deploy any application) if > > can be redirected to console, it would avoid looking up into Catalina log > > file while looking for progress of the server startup (deploying all apps). > > > > "INFO [Catalina-utility-2] > > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > > application directory" > > > Have you looked at the logging documentation? (Use the page for the Tomcat > version you’re actually using.) > > https://tomcat.apache.org/tomcat-10.1-doc/logging.html > > Look at the logging.properties example near the bottom of the page to see how > to associate handlers with Tomcat facilities. > > - Chuck
