-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manuel,
On 4/5/12 2:47 PM, manuel aldana wrote: > Inside JSP we have a backing model, which contains the dynamic data > to be displayed inside JSP. Itself the model is held quite simple, > but due to programming errors it can happen, that null-references > occur. This is very rare, but we need to be notified somehow (due > to explicit ERROR logging). The log to catalina.log isn't > sufficient for our log setup (we use graylog2-server). > > With bug@tomcat I meant that it error.jsp forwarding is not > consistent between an exception at the "very start" of JSP > rendering (e.g. syntax error) vs. error later during rendering. But > I agree there is no way to "revert" status codes and content once > bytes are sent to http-consumer. Right.... this can't possibly be attributed to a bug in Tomcat. Instead, one might say that this is simply a fact of life for streaming data applications. Your only recourse is bigger buffers. > What I will do create an interceptor which checks for the > combination of 200 status-code and exception. I'm not sure how you would scan for that, other than a filter that simply records all exceptions that are thrown (which is easy to do). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk999/8ACgkQ9CaO5/Lv0PAc6ACgsUM0qx5VN6+6496za7tUWrtr HggAn3pd1bX/Z8xlOrfBCGUummqvHQQw =ZGL3 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
