You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Tim N <tn...@gmail.com> on 2025/04/03 04:34:52 UTC
Re: Tomcat 10.1 Upgrade & Uber JAR Error
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 <tn...@gmail.com> wrote:
> 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 <tn...@gmail.com> 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.34, one of my applications is now throwing
>>
>> java.lang.NullPointerException: Cannot invoke
>> "org.apache.jasper.compiler.TldCache.getTldResourcePath(String)" because
>> the return value of "org.apache.jasper.Options.getTldCache()" is null
>>
>> The JARs are:
>> commons-codec-1.15.jar
>> ecj-3.33.0.jar
>> tomcat-annotations-api-10.1.34.jar
>> tomcat-api-10.1.34.jar
>> tomcat-catalina-10.1.34.jar
>> tomcat-catalina-ha-10.1.34.jar
>> tomcat-coyote-10.1.34.jar
>> tomcat-el-api-10.1.34.jar
>> tomcat-embed-core-10.1.34.jar
>> tomcat-embed-el-10.1.34.jar
>> tomcat-embed-jasper-10.1.34.jar
>> tomcat-embed-websocket-10.1.34.jar
>> tomcat-jaspic-api-10.1.34.jar
>> tomcat-jdbc-10.1.34.jar
>> tomcat-jni-10.1.34.jar
>> tomcat-jsp-api-10.1.34.jar
>> tomcat-juli-10.1.34.jar
>> tomcat-servlet-api-10.1.34.jar
>> tomcat-tribes-10.1.34.jar
>> tomcat-util-10.1.34.jar
>> tomcat-util-scan-10.1.34.jar
>>
>> Any ideas why this would be a problem with a more recent version?
>>
>>
Re: Tomcat 10.1 Upgrade & Uber JAR Error
Posted by Tim N <tn...@gmail.com>.
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 <ma...@apache.org> 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 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 issue in your code then maybe an issue in Jar scanning that
> identifies SCIs.
>
> No changes jump out as relevant for 10.1.23 and 10.1.39. Debugging the
> start up process is probably the quickest way to find the root cause.
>
> Mark
>
>
> >
> > On Sat, Feb 8, 2025 at 6:36 AM Tim N <tn...@gmail.com> wrote:
> >
> >> 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 <tn...@gmail.com> 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.34, one of my applications is now
> throwing
> >>>
> >>> java.lang.NullPointerException: Cannot invoke
> >>> "org.apache.jasper.compiler.TldCache.getTldResourcePath(String)"
> because
> >>> the return value of "org.apache.jasper.Options.getTldCache()" is null
> >>>
> >>> The JARs are:
> >>> commons-codec-1.15.jar
> >>> ecj-3.33.0.jar
> >>> tomcat-annotations-api-10.1.34.jar
> >>> tomcat-api-10.1.34.jar
> >>> tomcat-catalina-10.1.34.jar
> >>> tomcat-catalina-ha-10.1.34.jar
> >>> tomcat-coyote-10.1.34.jar
> >>> tomcat-el-api-10.1.34.jar
> >>> tomcat-embed-core-10.1.34.jar
> >>> tomcat-embed-el-10.1.34.jar
> >>> tomcat-embed-jasper-10.1.34.jar
> >>> tomcat-embed-websocket-10.1.34.jar
> >>> tomcat-jaspic-api-10.1.34.jar
> >>> tomcat-jdbc-10.1.34.jar
> >>> tomcat-jni-10.1.34.jar
> >>> tomcat-jsp-api-10.1.34.jar
> >>> tomcat-juli-10.1.34.jar
> >>> tomcat-servlet-api-10.1.34.jar
> >>> tomcat-tribes-10.1.34.jar
> >>> tomcat-util-10.1.34.jar
> >>> tomcat-util-scan-10.1.34.jar
> >>>
> >>> Any ideas why this would be a problem with a more recent version?
> >>>
> >>>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Tomcat 10.1 Upgrade & Uber JAR Error
Posted by Mark Thomas <ma...@apache.org>.
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 issue in your code then maybe an issue in Jar scanning that
identifies SCIs.
No changes jump out as relevant for 10.1.23 and 10.1.39. Debugging the
start up process is probably the quickest way to find the root cause.
Mark
>
> On Sat, Feb 8, 2025 at 6:36 AM Tim N <tn...@gmail.com> wrote:
>
>> 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 <tn...@gmail.com> 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.34, one of my applications is now throwing
>>>
>>> java.lang.NullPointerException: Cannot invoke
>>> "org.apache.jasper.compiler.TldCache.getTldResourcePath(String)" because
>>> the return value of "org.apache.jasper.Options.getTldCache()" is null
>>>
>>> The JARs are:
>>> commons-codec-1.15.jar
>>> ecj-3.33.0.jar
>>> tomcat-annotations-api-10.1.34.jar
>>> tomcat-api-10.1.34.jar
>>> tomcat-catalina-10.1.34.jar
>>> tomcat-catalina-ha-10.1.34.jar
>>> tomcat-coyote-10.1.34.jar
>>> tomcat-el-api-10.1.34.jar
>>> tomcat-embed-core-10.1.34.jar
>>> tomcat-embed-el-10.1.34.jar
>>> tomcat-embed-jasper-10.1.34.jar
>>> tomcat-embed-websocket-10.1.34.jar
>>> tomcat-jaspic-api-10.1.34.jar
>>> tomcat-jdbc-10.1.34.jar
>>> tomcat-jni-10.1.34.jar
>>> tomcat-jsp-api-10.1.34.jar
>>> tomcat-juli-10.1.34.jar
>>> tomcat-servlet-api-10.1.34.jar
>>> tomcat-tribes-10.1.34.jar
>>> tomcat-util-10.1.34.jar
>>> tomcat-util-scan-10.1.34.jar
>>>
>>> Any ideas why this would be a problem with a more recent version?
>>>
>>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org