https://bz.apache.org/bugzilla/show_bug.cgi?id=60497
--- Comment #5 from Wai-Kau Lo <w...@destinysolutions.com> --- I think the JSP spec clearly states that we should not reuse a JSP tag instance if its doStartTag method execution raises an exception, as I explained in my previous comment. Also, this is clearly a regression issue introduced by changset set 1754112 in Tomcat 8.5.5, which fortunately has not been ported back to the Tomcat 9.0 release branch. I am hoping we can roll back this changeset in the Tomcat 8.5 release branch. Finally, JSP Custom Tag Pooling has been highlighted in the "Jasper 2 JSP Engine How To" section as a significant performance booster. JSP Custom Tag Pooling - The java objects instantiated for JSP Custom Tags can now be pooled and reused. This significantly boosts the performance of JSP pages which use custom tags. Since our application depends heavily on custom tags, I am just hesitant to simply turn off tag pooling with conducting some performance tests first. In the meantime, I guess the only recourse is to compile my own Jasper engine. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
