Repository navigation
[🐛 Bug]: [GRID] logging.properties is ignored when trying to remove stack trace errors from Logs #14160
Description
Activity
- addedI-defectSomething is not working as intendedSomething is not working as intendedA-needs-triagingA Selenium member will evaluate this soon!A Selenium member will evaluate this soon!
on Jun 20, 2024 github-actions commented
on Jun 20, 2024 on Jun 20, 2024 – with GitHub ActionsContributorMore actions@KrzysztofC, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
Triage this issue by using labels.
If information is missing, add a helpful comment and then
I-issue-templatelabel.If the issue is a question, add the
I-questionlabel.If the issue is valid but there is no time to troubleshoot it, consider adding the
help wantedlabel.If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable
G-*label, and it will provide the correct link and auto-close the issue.After troubleshooting the issue, please add the
R-awaiting answerlabel.Thank you!
- addedB-gridEverything grid and server relatedEverything grid and server relatedand removedA-needs-triagingA Selenium member will evaluate this soon!A Selenium member will evaluate this soon!
on Jul 12, 2024 I'm noticing that this issue stems from the fact that any logging configuration with a
logging.propertiesfile is overwritten and replaced with the custom Selenium formatters and handlers (SeeconfigureLogging()function on line 96 ofselenium/java/src/org/openqa/selenium/grid/log/LoggingOptions.java). This can be fixed by simply checking if thehandlersproperty if theLogManageris null or not, but is it an intention of selenium to not allow custom configured logging?- added a commit that references this issue
on Nov 13, 2024 - added a commit that references this issue
on Dec 28, 2024 github-actions commented
on Jan 27, 2025 on Jan 27, 2025 – with GitHub ActionsContributorMore actionsThis issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.
- locked and limited conversation to collaborators
on Jan 27, 2025 - added 2 commits that reference this issue
on Jan 31, 2025 - added 2 commits that reference this issue
on Mar 23, 2025 - added a commit that references this issue
on May 17, 2025
What happened?
When using:
-Djava.util.logging.config.file=/opt/logging.properties
which contains:
handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=INFO
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.SimpleFormatter.format=%1$tF %1$tT.%1$tL %4$s: %3$s %5$s %n
this works in other Java app that uses java.util.logging for logging, but it has zero effect on Grid Logs.
How can we reproduce the issue?
Relevant log output
Operating System
RH8 and Win10
Selenium version
4.21.0
What are the browser(s) and version(s) where you see this issue?
N/A
What are the browser driver(s) and version(s) where you see this issue?
N/A
Are you using Selenium Grid?
4.21.0