-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Stack traces exceeding 100 lines #7207
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
Comments
|
Stack trace 2: A request attribute is supplied as null to the freemarker template view's dropdown tag 2016-10-23 10:14:28.786 ERROR 9192 --- [nio-8080-exec-9] freemarker.runtime : Error executing FreeMarker template freemarker.core._MiscTemplateException: When calling macro "formSingleSelect", required parameter "options" (parameter #2) was specified, but had null/missing value. Tip: If the parameter value expression on the caller side is known to be legally null/missing, you may want to specify a default value for it with the "!" operator, like paramValue!defaultValue.FTL stack trace ("~" means nesting-related): - Reached through: #include "/main.ftl" [in template "index.ftl" at line 2, column 1]
===============afterCompletion============== Tip: If the parameter value expression on the caller side is known to be legally null/missing, you may want to specify a default value for it with the "!" operator, like paramValue!defaultValue.FTL stack trace ("~" means nesting-related): freemarker.core._MiscTemplateException: When calling macro "formSingleSelect", required parameter "options" (parameter #2) was specified, but had null/missing value. Tip: If the parameter value expression on the caller side is known to be legally null/missing, you may want to specify a default value for it with the "!" operator, like paramValue!defaultValue.FTL stack trace ("~" means nesting-related): - Reached through: #include "/main.ftl" [in template "index.ftl" at line 2, column 1]
|
The mechanism that we have in place for hiding stack traces when they are not helpful only applies to failures that occur during application start up. Furthermore, it has to be an exception that Spring Boot code is catching so that we can decide what to do with it. When a failure occurs at runtime, there's nowhere that Spring Boot can reliably catch the exception and decide what to do with it. Unfortunately, the two examples above fall into this second category so there's nothing that we can do about them with the current mechanism. For more general manipulation or shortening of exception stack traces please see #4451 and #3223.
We focussed solely on exceptions that occur during start up. We prioritised those that we believe to be quite common and where the stack trace doesn't really provide any valuable information. |
Problem: Spring boot spitting 100s of lines of stack traces.
I understand you are working on shortening some of the stack traces to be short. As per phil webb's twitter comments I will be posting some stack traces that I encounter. I am not sure if they are high frequency issues and respectively if they need to prioritized.
I will post a few more in the next few days. So, please keep this ticket open for me to add stack traces as updates. Please update the ticket with the details of how you pick which stack traces you prioritized.
The text was updated successfully, but these errors were encountered: