Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display full stack trace of exception that occurs on startup #5102

Closed
timorantalaiho opened this issue Feb 12, 2014 · 1 comment
Closed

Display full stack trace of exception that occurs on startup #5102

timorantalaiho opened this issue Feb 12, 2014 · 1 comment

Comments

@timorantalaiho
Copy link
Contributor

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

{2.0.0-SNAPSHOT}: Startup Failed ...
- NumberFormatException[For input string: ""]

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.

@javanna
Copy link
Member

javanna commented Feb 21, 2014

Oh oh, closed the wrong issue, sorry :)

@javanna javanna reopened this Feb 21, 2014
@javanna javanna closed this as completed in 3ae02b0 Apr 4, 2014
javanna pushed a commit that referenced this issue Apr 4, 2014
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants