You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an exception is raised by code triggered from Bootstrap class, only its message (and the message of the possible cause stack) is displayed, not the full stack trace.
This means that if for example some plugin reads a System property that it expects to be numeric but which is accidentally set as empty, you only see something like this
I propose the whole stack trace would be displayed in these cases, either on System.err when no logging is configured or on ERROR level via log4j. This would make these kinds of configuration errors loads easier to debug, with the small price of uglier error messages.
Pull request is coming up.
The text was updated successfully, but these errors were encountered:
Whether or not the stacktrace is displayed is controlled by bootstrap
log level setting, so that bootstrap: DEBUG displays the stack trace on
output, like it does on log
Closes#5102
If an exception is raised by code triggered from Bootstrap class, only its message (and the message of the possible cause stack) is displayed, not the full stack trace.
This means that if for example some plugin reads a System property that it expects to be numeric but which is accidentally set as empty, you only see something like this
I propose the whole stack trace would be displayed in these cases, either on System.err when no logging is configured or on ERROR level via log4j. This would make these kinds of configuration errors loads easier to debug, with the small price of uglier error messages.
Pull request is coming up.
The text was updated successfully, but these errors were encountered: