Bug 66031

Summary: JasperInitializer not correctly initialized when a Default JspFactory is already defined
Product: Tomcat 10 Reporter: jlmonteiro <jlmonteiro>
Component: JasperAssignee: Tomcat Developers Mailing List <dev>
Severity: normal CC: jlmonteiro
Priority: P2    
Version: 10.0.20   
Target Milestone: ------   
Hardware: PC   
OS: All   

Description jlmonteiro@apache.org 2022-04-25 14:50:24 UTC
An issue as been introduced in JasperInitializer with commit 5e8eb55

When a default JspFactory is already defined the static field defaultFactory in JasperInitializer isn't initialized. It produces a NullPointerException line 108 when setting the poolSize.

This fix enforces a proper initialization even when the default JspFactory is already set.

PR available https://github.com/apache/tomcat/pull/505
Comment 1 Remy Maucherat 2022-04-25 16:06:53 UTC
Ok, the field is gone, and the testcase is integrated. Sorry for the trouble.
The fix will be in 10.1.0-M15 and 10.0.21.