matrei commented on PR #15564:
URL: https://github.com/apache/grails-core/pull/15564#issuecomment-4215111039

   > Why not change the default configuration to just hide logs from 
grails-bootstrap/src/main/groovy/org/grails/exceptions/reporting/DefaultStackTraceFilterer.java
 then there wouldn't be a duplicate log right?
   
   Yes, that might be one option/solution!
   But I wonder if logging the stacktrace 4 times is the right behavior?
   
   ```xml
   <logger name="StackTrace" level="OFF" />
   ```
   
   ```console
   >                                                                            
<
   >                            ____           _ _                              
<
   >                           / ___|_ __ __ _(_) |___                          
<
   >                          | |  _| '__/ _` | | / __|                         
<
   >                          | |_| | | | (_| | | \__ \                         
<
   >                           \____|_|  \__,_|_|_|___/                         
<
   >                          https://grails.apache.org                         
<
   >                                                                            
<
               grails-test-examples-app5: 0.1 | JVM: BellSoft 17.0.18           
 
           Grails: 8.0.0-SNAPSHOT | Groovy: 4.0.31 | Spring Boot: 3.5.13        
 
                                   Spring: 6.2.17                               
 
   
   Grails application running at http://localhost:8080 in environment: 
development
   2026-04-09 16:33:53.713 ERROR --- [nio-8080-exec-1] 
o.g.web.errors.GrailsExceptionResolver   : MissingPropertyException occurred 
when processing request: [GET] /target/show
   No such property: notHere for class: app5.TargetController. Stacktrace 
follows:
   
   java.lang.reflect.InvocationTargetException
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at 
org.grails.core.DefaultGrailsControllerClass$ReflectionInvoker.invoke(DefaultGrailsControllerClass.java:215)
        at 
org.grails.core.DefaultGrailsControllerClass.invoke(DefaultGrailsControllerClass.java:192)
        at 
org.grails.web.mapping.mvc.UrlMappingsInfoHandlerAdapter.handle(UrlMappingsInfoHandlerAdapter.groovy:110)
        at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1089)
        at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:979)
        at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
        at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:903)
        at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:885)
        at 
org.grails.web.servlet.mvc.GrailsWebRequestFilter.doFilterInternal(GrailsWebRequestFilter.java:80)
        at 
org.grails.web.filters.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:70)
        at java.base/java.lang.Thread.run(Thread.java:840)
   Caused by: groovy.lang.MissingPropertyException: No such property: notHere 
for class: app5.TargetController
        at 
grails.artefact.gsp.TagLibraryInvoker$Trait$Helper.propertyMissing(TagLibraryInvoker.groovy:125)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at app5.TargetController.display(TargetController.groovy:41)
   Caused by: groovy.lang.MissingPropertyException: No such property: notHere 
for class: app5.TargetController
   
        at app5.TargetController.show(TargetController.groovy:37)
        ... 13 common frames omitted
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to