The issue occurred again in Tomcat v10.1.40 but is fixed again in Tomcat
v10.1.41
On Thu, Apr 3, 2025 at 7:52 PM Mark Thomas wrote:
> On 03/04/2025 05:34, Tim N wrote:
> > That should have been
> >> Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
> >
> > ...and now looks li
On 03/04/2025 05:34, Tim N wrote:
That should have been
Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
...and now looks like this was first fixed again in v10.1.39
Any ideas why?
It suggests that the JasperInitializer was not trigger on start. If not
a packaging issu
That should have been
> Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
...and now looks like this was first fixed again in v10.1.39
Any ideas why?
On Sat, Feb 8, 2025 at 6:36 AM Tim N wrote:
> Looks like this last worked Tomcat v10.1.20 and first failed v19.1.23
>
> On F
Looks like this last worked Tomcat v10.1.20 and first failed v19.1.23
On Fri, Feb 7, 2025 at 3:22 PM Tim N wrote:
> I was launching my application successfully with Tomcat 10.1.16 using a
> JAR with all dependencies in a single JAR via "maven-assembly-plugin".
>
> Since upgrading to Tomcat 10.1.
