REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Divyabharathi Sundaram 
Hi Team,

We have recently upgraded tomcat from 9.0.82 to 9.0.96, one of the application 
teams has reported the error below ( please refer the screenshot). They have 
also stated that the issue is because of the bug with the version 9.0.96. 
Please confirm whether the version 9.0.96 is reported as a bug for the below 
issue. If yes, please let us know the stable tomcat version or workaround to 
resolve this.

[cid:a5cf12d2-3112-4324-89c1-8908d85ee121]

Regards,

DivyaBharathi.S

TCS - Infra Midrange SME

Malaysia Airlines Berhad



Malaysia Aviation Group Disclaimer: "The message and any files attached is 
intended solely for the use of the person to whom it is addressed and may 
contain information that is confidential and privileged under applicable laws. 
If you are not the intended recipient, you are hereby notified that any use, 
review, disclosure, copying, printing, distribution or dissemination of this 
message is prohibited. We take no responsibility of any reliance that you may 
place on this message and we further take no responsibility for any viruses or 
other damaging elements that may be contained in this email together with any 
of its attachments. If you have received this message in error, please notify 
us by return email and arrangements will be made to retrieve the same from you."

Re: REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Sebastian Trost 

DivyaBharathi,

please don't attach or link images in your e-mails. Instead, just 
copy&paste the error as text into your message.


Sebastian

On 06.02.2025 09:06, Divyabharathi Sundaram wrote:

Hi Team,

We have recently upgraded tomcat from 9.0.82 to 9.0.96, one of the 
application teams has reported the error below ( please refer the 
screenshot). They have also stated that the issue is because of the 
bug with the version 9.0.96. Please confirm whether the version 9.0.96 
is reported as a bug for the below issue. If yes, please let us know 
the stable tomcat version or workaround to resolve this.



Regards,

*DivyaBharathi.S*

TCS - Infra Midrange SME

Malaysia Airlines Berhad

Malaysia Aviation Group Disclaimer: "The message and any files 
attached is intended solely for the use of the person to whom it is 
addressed and may contain information that is confidential and 
privileged under applicable laws. If you are not the intended 
recipient, you are hereby notified that any use, review, disclosure, 
copying, printing, distribution or dissemination of this message is 
prohibited. We take no responsibility of any reliance that you may 
place on this message and we further take no responsibility for any 
viruses or other damaging elements that may be contained in this email 
together with any of its attachments. If you have received this 
message in error, please notify us by return email and arrangements 
will be made to retrieve the same from you." 



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Dimitris Soumis 
On Thu, Feb 6, 2025 at 10:13 AM Divyabharathi Sundaram
 wrote:

> Hi Team,
>
> We have recently upgraded tomcat from 9.0.82 to 9.0.96, one of the
> application teams has reported the error below ( please refer the
> screenshot). They have also stated that the issue is because of the bug
> with the version 9.0.96. Please confirm whether the version 9.0.96 is
> reported as a bug for the below issue. If yes, please let us know the
> stable tomcat version or workaround to resolve this.
>
Since there is no error provided, can't propose possible fixes if any.
However, the latest stable tomcat 9 version is *9.0.99*.

>
>
> Regards,
>
> *DivyaBharathi.S*
>
> TCS - Infra Midrange SME
>
> Malaysia Airlines Berhad
>
>
> Malaysia Aviation Group Disclaimer: "The message and any files attached is
> intended solely for the use of the person to whom it is addressed and may
> contain information that is confidential and privileged under applicable
> laws. If you are not the intended recipient, you are hereby notified that
> any use, review, disclosure, copying, printing, distribution or
> dissemination of this message is prohibited. We take no responsibility of
> any reliance that you may place on this message and we further take no
> responsibility for any viruses or other damaging elements that may be
> contained in this email together with any of its attachments. If you have
> received this message in error, please notify us by return email and
> arrangements will be made to retrieve the same from you."
>

Re: REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Dimitris Soumis 
Apologies, misspelled the version. As of 06/02/2025,*  9.0.98* is the
latest stable tomcat 9 version .

Kind regards,
Dimitris

On Thu, Feb 6, 2025 at 12:44 PM Dimitris Soumis  wrote:

>
>
> On Thu, Feb 6, 2025 at 10:13 AM Divyabharathi Sundaram
>  wrote:
>
>> Hi Team,
>>
>> We have recently upgraded tomcat from 9.0.82 to 9.0.96, one of the
>> application teams has reported the error below ( please refer the
>> screenshot). They have also stated that the issue is because of the bug
>> with the version 9.0.96. Please confirm whether the version 9.0.96 is
>> reported as a bug for the below issue. If yes, please let us know the
>> stable tomcat version or workaround to resolve this.
>>
> Since there is no error provided, can't propose possible fixes if any.
> However, the latest stable tomcat 9 version is *9.0.99*.
>
>>
>>
>> Regards,
>>
>> *DivyaBharathi.S*
>>
>> TCS - Infra Midrange SME
>>
>> Malaysia Airlines Berhad
>>
>>
>> Malaysia Aviation Group Disclaimer: "The message and any files attached
>> is intended solely for the use of the person to whom it is addressed and
>> may contain information that is confidential and privileged under
>> applicable laws. If you are not the intended recipient, you are hereby
>> notified that any use, review, disclosure, copying, printing, distribution
>> or dissemination of this message is prohibited. We take no responsibility
>> of any reliance that you may place on this message and we further take no
>> responsibility for any viruses or other damaging elements that may be
>> contained in this email together with any of its attachments. If you have
>> received this message in error, please notify us by return email and
>> arrangements will be made to retrieve the same from you."
>>
>

Re: Building tomcat-native on RHEL 8

2025-02-06 Thread Dimitris Soumis 
On Wed, Feb 5, 2025 at 7:58 PM Darryl Baker 
wrote:

> I could if there was one. Red Hat stopped having Tomcat in the OS
> distribution and is now part of the JBoss product the University decided
> not to buy.
>
Tomcat is available in the OS distribution other than the Jboss web server
product. Tomcat-native is not.

> [root@XXX] tomcat-native-2.0.8-src]# yum search tomcat-native
> Updating Subscription Management repositories.
> No matches found.
> [root@XXX] tomcat-native-2.0.8-src]#
>
> Darryl Baker, GSEC, GCLD (he/him/his)
> Sr. System Administrator
> Distributed Application Platform Services
> Northwestern University
>
>
>
>
> On 2/4/25, 4:21 PM, "Christopher Schultz"  > wrote:
>
>
> Darryl,
>
>
> On 2/3/25 1:17 PM, Darryl Baker wrote:
> > Would someone please point me to the documentation on building
> tomcat-native on RHEL 8 using the Red Hat supplied APR package?
>
>
> Do you need to build from source, or can you use the RHEL binary?
>
>
> $ sudo yum search tomcat-native
> = Name Exactly Matched: tomcat-native =
> tomcat-native.x86_64 : Tomcat native library
>
>
> If you truly need to build, we can probably update the documentation to
> indicate which popular packages would be necessary before building from
> source.
>
>
> -chris
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org  users-unsubscr...@tomcat.apache.org>
> For additional commands, e-mail: users-h...@tomcat.apache.org  users-h...@tomcat.apache.org>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

Re: Building tomcat-native on RHEL 8

2025-02-06 Thread Dimitris Soumis 
I will try to provide you with a step-by-step guide for a RHEL 8 vanilla
installation. Please feel free to tweak according to your needs.

1) Make sure the required packages are installed:
$ *dnf install apr-devel openssl-devel java-11-openjdk-devel*

2) Fetch the tomcat-native from the official site
$ *wget
https://dlcdn.apache.org/tomcat/tomcat-connectors/native/1.3.1/source/tomcat-native-1.3.1-src.tar.gz
*
(Optional but recommended: Compare the hashes found at
https://tomcat.apache.org/download-native.cgi)

3) Extract the compressed file and move to the native directory:
$ *tar -xvf tomcat-native-1.3.1-src.tar.gz && cd
tomcat-native-1.3.1-src/native/*

4) Run the configuration script:
$ *./configure --with-java-home=$(dirname $(dirname $(readlink $(readlink
$(which javac)*
(You can simply replace
`--with-java-home=/usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64` .
The command above conveniently detects the relevant path.)

The logs will be something like the following:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for working mkdir -p... yes
Tomcat Native Version: 1.3.1
checking for chosen layout... tcnative
checking for APR... yes
configure: APR 1.6.3 detected.
  setting CC to "gcc"
  setting CPP to "gcc -E"
checking JAVA_HOME... /usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64
  adding "-I/usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64/include"
to TCNATIVE_PRIV_INCLUDES
checking for JDK os include directory...  linux
  adding
"-I/usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64/include/linux" to
TCNATIVE_PRIV_INCLUDES
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for OpenSSL library... using openssl from /usr/lib64 and
/usr/include
checking OpenSSL library version >= 1.1.1... ok
checking for OpenSSL DSA support... yes
  setting TCNATIVE_LDFLAGS to "-lssl -lcrypto"
  adding "-DHAVE_OPENSSL" to CFLAGS
  setting TCNATIVE_LIBS to ""
  setting TCNATIVE_LIBS to " /usr/lib64/libapr-1.la  -lpthread -ldl"
  adding "-DTCNATIVE_LINUX" to CFLAGS
checking for apr_pollset_wakeup in -lapr-1... yes
  adding "-DHAVE_POLLSET_WAKEUP" to CFLAGS
configure: creating ./config.status
config.status: creating Makefile
config.status: executing default commands

You can tweak the configure script at your needs. By running `*./configure
--help*` you will see all the arguments that can be provided.

5) Build the libraries:
$ *make*
(There is a high probability that you'll face the following error on a rhel
machine : `gcc: error: /usr/lib/rpm/redhat/redhat-hardened-cc1: No such
file or directory` . This can be resolved by installing $ dnf install
redhat-rpm-config rpm-build . Rerun the make command)

6) Install the libraries:
$ *make install *

7) The default installation path is /usr/local/apr/lib/ (since we have not
provided a value to the --prefix argument of the configure script). By
listing the files, you should see the following:
$ *ls /usr/local/apr/lib/*
libtcnative-1.a  libtcnative-1.la  libtcnative-1.so  libtcnative-1.so.0
 libtcnative-1.so.0.3.1

I hope this clears it up for you.

Kind regards,
Dimitris

On Thu, Feb 6, 2025 at 2:39 AM Darryl Baker 
wrote:

> Trying to build 1.3.1 I did the fit manipulations as suggested (I know
> very little about git) and I get
> [root@evfediamdv1 tomcat-native-1.3.1-src]# ./jnirelease.sh -f
> --with-apr=/root/rpmbuild/SOURCES/apr-1.6.3 --ver=1.3.1
>
> Using apr source from: `/root/rpmbuild/SOURCES/apr-1.6.3'
> Using: /bin/elinks -dump -dump-width 80 -dump-charset iso-8859-1
> -no-numbering -no-references -no-home ...
> Using /bin/perl
> Using GIT repo   : `
> https://gitbox.apache.org/repos/asf/tomcat-native.git`
> 
> Using version: `1.3.1`
> HEAD is now at 0d6da8c122 Tag Tomcat Native 1.3.1
> Fetching tcjava
> WARNING: git subtree is not up to date with
>  https://gitbox.apache.org/repos/asf/tomcat.git
>  Either correct now by running
>  'git checkout 1.3.x'
>  'git rm -rf java/org/apache/tomcat/jni'
>  'git read-tree --prefix=java/org/apache/tomcat/jni/ -u
> tcjava/9.0.x:java/org/apache/tomcat/jni'
>  'git commit'
>  or run this script with -f (force)
> FORCED run chosen
> #define TCN_IS_DEV_VERSION  0
> Buildfile:
> /usr/local/src/tomcat-native-1.3.1-src/tomcat-native-1.3.1-src/xdocs/build.xml
>
> buil

Re: Building tomcat-native on RHEL 8

2025-02-06 Thread Rainer Jung 



Am 06.02.25 um 18:18 schrieb Darryl Baker:
> My question is why is tomcat-native dependent on APR at all? Could it 
be built without that dependency?


The APR library originates in the Apache httpd project. The project 
decided long ago, to split out some very basic functionality into a 
separate library trying to encapsulate OS specific code in it. This 
library is called APR (Apache Portable Runtime) or libapr. A second one 
is celled APR Util (APR Utilities or libapr-util) which contains higher 
level code but is not relevant to tcnative.


The tcnative library contains functionality that hooks into Tomcat and 
uses some the APR library as an implementation of its lower level 
functionality.


In order to use tcnative (confusingly sometimes also called the APR 
connector) inside Tomcat you need both, the tcnative library and the APR 
library.


And to build tcnative yourself you also need the APR library and its 
header files (the devel package) plus OpenSSL and its header files.


Since APR is much older and also needed by the Apache httpd web server, 
most Linux distributions provide the APR library binaries (and header 
files) in the form of a distribution package. So you do not need to 
build this by yourself, just install it.


Many distributions do not provide packages for tcnative, so you do need 
to build it yourself.


> Can I build tomcat native on Rocky Linux? Then could I use it on Red 
Hat? Has anyone tried that?


Currently RHEL and Rocky are binary compatible assuming that you are 
using the same versions of them. You can build your binary on any of 
those and use it on the other one.


Best regards,

Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reg: Tomcat temp file deletion

2025-02-06 Thread Jalaj Asher 
Hello,
Is it ok to delete files from tomcat/temp folder  while the tomcat is running ?

It required to restart the tomcats post deletion of the files in tomcat/temp 
folder  or should it be deleted only post stopping the tomcat service ?




CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains confidential 
information belonging to the sender that is legally privileged and proprietary 
and may be subject to protection under the law, including the Health Insurance 
Portability and Accountability Act (HIPAA). If you are not the intended 
recipient of this e-mail, you are prohibited from sharing, copying, or 
otherwise using or disclosing its contents. If you have received this e-mail in 
error, please notify the sender immediately by reply e-mail and permanently 
delete this e-mail and any attachments without reading, forwarding or saving 
them. Thank you.

Re: Building tomcat-native on RHEL 8

2025-02-06 Thread Dimitris Soumis 
Rainer, your mail has not popped up when I sent mine.
Thanks for the detailed description :)

Kind regards,
Dimitris

On Thu, Feb 6, 2025 at 9:14 PM Dimitris Soumis  wrote:

>
>
> On Thu, Feb 6, 2025 at 7:30 PM Darryl Baker 
> wrote:
>
>> My question is why is tomcat-native dependent on APR at all? Could it be
>> built without that dependency?
>>
> Tomcat Native relies on the Apache Portable Runtime (APR) to bridge the
> gap between Tomcat, and native OS capabilities. APR provides APIs that map
> to the OS. Tomcat Native is able to provide the performance increases due
> to apr bypassing Java’s virtualized layer. So no, tomcat-native can not be
> built without that dependency.
>
>> Can I build tomcat native on Rocky Linux? Then could I use it on Red Hat?
>> Has anyone tried that?
>>
>  The building process of tomcat native is OS agnostic. As long as the
> required dependencies are provided to the building process, everything
> should work flawlessly.
> However, for the libraries produced in one system to work with another
> system depends on factors such as the other system having equal various
> library versions like glibc or OpenSSL, equal cpu architecture etc.
>
>> Darryl Baker, GSEC, GCLD (he/him/his)
>> Sr. System Administrator
>> Distributed Application Platform Services
>> Northwestern University
>> 4th Floor
>> 2020 Ridge Avenue
>> Evanston, IL 60208-0801
>> darryl.ba...@northwestern.edu 
>> (847) 467-6674 
>>
>>
>>
>>
>> On 2/6/25, 4:26 AM, "Dimitris Soumis" > dsou...@apache.org>> wrote:
>>
>>
>> On Wed, Feb 5, 2025 at 7:58 PM Darryl Baker <
>> darryl.ba...@northwestern.edu >
>> wrote:
>>
>>
>> > I could if there was one. Red Hat stopped having Tomcat in the OS
>> > distribution and is now part of the JBoss product the University decided
>> > not to buy.
>> >
>> Tomcat is available in the OS distribution other than the Jboss web server
>> product. Tomcat-native is not.
>>
>>
>> > [root@XXX] tomcat-native-2.0.8-src]# yum search tomcat-native
>> > Updating Subscription Management repositories.
>> > No matches found.
>> > [root@XXX] tomcat-native-2.0.8-src]#
>> >
>> > Darryl Baker, GSEC, GCLD (he/him/his)
>> > Sr. System Administrator
>> > Distributed Application Platform Services
>> > Northwestern University
>> >
>> >
>> >
>> >
>> > On 2/4/25, 4:21 PM, "Christopher Schultz" > 
>> >  ch...@christopherschultz.net>>> wrote:
>> >
>> >
>> > Darryl,
>> >
>> >
>> > On 2/3/25 1:17 PM, Darryl Baker wrote:
>> > > Would someone please point me to the documentation on building
>> > tomcat-native on RHEL 8 using the Red Hat supplied APR package?
>> >
>> >
>> > Do you need to build from source, or can you use the RHEL binary?
>> >
>> >
>> > $ sudo yum search tomcat-native
>> > = Name Exactly Matched: tomcat-native =
>> > tomcat-native.x86_64 : Tomcat native library
>> >
>> >
>> > If you truly need to build, we can probably update the documentation to
>> > indicate which popular packages would be necessary before building from
>> > source.
>> >
>> >
>> > -chris
>> >
>> >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > users-unsubscr...@tomcat.apache.org> > > users-unsubscr...@tomcat.apache.org > users-unsubscr...@tomcat.apache.org>>
>> > For additional commands, e-mail: users-h...@tomcat.apache.org > users-h...@tomcat.apache.org> > > users-h...@tomcat.apache.org >
>> >
>> >
>> >
>> >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > users-unsubscr...@tomcat.apache.org>
>> > For additional commands, e-mail: users-h...@tomcat.apache.org > users-h...@tomcat.apache.org>
>> >
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>

Re: Building tomcat-native on RHEL 8

2025-02-06 Thread Darryl Baker 
Thank you. 

Darryl Baker, GSEC, GCLD (he/him/his) 
Sr. System Administrator 
Distributed Application Platform Services 
Northwestern University 
4th Floor 
2020 Ridge Avenue 
Evanston, IL 60208-0801 
darryl.ba...@northwestern.edu  
(847) 467-6674  




On 2/6/25, 4:35 AM, "Dimitris Soumis" mailto:dsou...@apache.org>> wrote:


I will try to provide you with a step-by-step guide for a RHEL 8 vanilla
installation. Please feel free to tweak according to your needs.


1) Make sure the required packages are installed:
$ *dnf install apr-devel openssl-devel java-11-openjdk-devel*


2) Fetch the tomcat-native from the official site
$ *wget
https://dlcdn.apache.org/tomcat/tomcat-connectors/native/1.3.1/source/tomcat-native-1.3.1-src.tar.gz
 


 
;>*
(Optional but recommended: Compare the hashes found at
https://tomcat.apache.org/download-native.cgi 
)


3) Extract the compressed file and move to the native directory:
$ *tar -xvf tomcat-native-1.3.1-src.tar.gz && cd
tomcat-native-1.3.1-src/native/*


4) Run the configuration script:
$ *./configure --with-java-home=$(dirname $(dirname $(readlink $(readlink
$(which javac)*
(You can simply replace
`--with-java-home=/usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64` .
The command above conveniently detects the relevant path.)


The logs will be something like the following:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for working mkdir -p... yes
Tomcat Native Version: 1.3.1
checking for chosen layout... tcnative
checking for APR... yes
configure: APR 1.6.3 detected.
setting CC to "gcc"
setting CPP to "gcc -E"
checking JAVA_HOME... /usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64
adding "-I/usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64/include"
to TCNATIVE_PRIV_INCLUDES
checking for JDK os include directory... linux
adding
"-I/usr/lib/jvm/java-11-openjdk-11.0.25.0.9-2.el8.x86_64/include/linux" to
TCNATIVE_PRIV_INCLUDES
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for OpenSSL library... using openssl from /usr/lib64 and
/usr/include
checking OpenSSL library version >= 1.1.1... ok
checking for OpenSSL DSA support... yes
setting TCNATIVE_LDFLAGS to "-lssl -lcrypto"
adding "-DHAVE_OPENSSL" to CFLAGS
setting TCNATIVE_LIBS to ""
setting TCNATIVE_LIBS to " /usr/lib64/libapr-1.la -lpthread -ldl"
adding "-DTCNATIVE_LINUX" to CFLAGS
checking for apr_pollset_wakeup in -lapr-1... yes
adding "-DHAVE_POLLSET_WAKEUP" to CFLAGS
configure: creating ./config.status
config.status: creating Makefile
config.status: executing default commands


You can tweak the configure script at your needs. By running `*./configure
--help*` you will see all the arguments that can be provided.


5) Build the libraries:
$ *make*
(There is a high probability that you'll face the following error on a rhel
machine : `gcc: error: /usr/lib/rpm/redhat/redhat-hardened-cc1: No such
file or directory` . This can be resolved by installing $ dnf install
redhat-rpm-config rpm-build . Rerun the make command)


6) Install the libraries:
$ *make install *


7) The default installation path is /usr/local/apr/lib/ (since we have not
provided a value to the --prefix argument of the configure script). By
listing the files, you should see the following:
$ *ls /usr/local/apr/lib/*
libtcnative-1.a libtcnative-1.la libtcnative-1.so libtcnative-1.so.0
libtcnative-1.so.0.3.1


I hope this clears it up for you.


Kind regards,
Dimitris


On Thu, Feb 6, 2025 at 2:39 AM Darryl Baker mailto:darryl.ba...@northwestern.edu>>
wrote:


> Trying to build 1.3.1 I did the fit manipulations as suggested (I know
> very little about git) and I get
> [root@evfediamdv1 tomcat-native-1.3.1-src]# ./jnirelease.sh -f
> --with-apr=/root/rpmbuild/SOURCES/apr-1.6.3 --ver=1.3.1
>
> Using apr source from: `/root/rpmbuild/SOURCES/apr-1.6.3'
> Using: /bin/elinks -dump -dump-width 80 -dump-charset iso-8859-1
> -no-numbering -no-references -no-home ...
> Using /bin/perl
> Using GIT repo : `
> https://gitbox.apache.org/repos/asf/tomcat-native.git 
> `
>

Re: REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Divyabharathi Sundaram 
Hi Dimitris,

Noted,  appreciate your advise on version 9.0.96.Below is the error and the 
application team have provided the reference link stating there is a bug in the 
version 9.0.96.

Link:
https://bz.apache.org/bugzilla/show_bug.cgi?id=69386#c0
69386 – Pre-compiled JSPs result in NoSuchMethodError with latest 
upgrade
There is no guarantee that previously generated code remains compatible with 
new Jasper runtime, this is untested and will remain that way. Also any fixes 
or optimizations occur in the generated code.
bz.apache.org

Messages:   
org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
java.lang.NoSuchMethodError: 
org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
javax.servlet.ServletException: java.lang.NoSuchMethodError: 
org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
File: org/apache/jsp/multiselect_jsp.java
Line number:  323
Stacktraces
org.apache.jasper.JasperException: javax.servlet.ServletException: 
java.lang.NoSuchMethodError: 
org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V

org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:623)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:489)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:376)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:324)
javax.servlet.http.HttpServlet.service(HttpServlet.java:623)

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168)

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)

org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:641)

org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:415)

org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:347)

org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:284)

org.apache.struts2.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:164)

org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResultSupport.java:186)

com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:367)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:271)

org.apache.struts2.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:256)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:100)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:100)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:138)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:238)

com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:238)

com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

com.opensymphony.xwork2.interceptor.StaticParametersInterceptor.intercept(StaticParametersInterceptor.java:191)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

org.apache.struts2.interceptor.MultiselectInterceptor.intercept(MultiselectInterceptor.java:73)

com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)

org.apache.struts2.interceptor.CheckboxInterceptor.intercept(CheckboxInterceptor.java:91)

com.opensymphony.xwork2.DefaultActionInvocation.inv

Re: REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Divyabharathi Sundaram 
Hi Dimitris,

Noted, Kindly hold the ticket we will get back after discussing with the 
application team.

Regards,

DivyaBharathi.S

TCS - Infra Midrange SME

Malaysia Airlines Berhad




From: Dimitris Soumis 
Sent: Thursday, February 6, 2025 10:31 PM
To: Tomcat Users List 
Subject: Re: REG: Version stability of Tomcat 9.0.96

CAUTION! This email originated from outside of MAG

Judging by the method call
JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/*Tag*
;Lorg/apache/tomcat/*InstanceManager*;*Z*) you are calling the method with
the 3 arguments of Tag, InstanceManager and boolean.

The only method definition in 9.0.96 is `*public static void releaseTag(Tag
tag, InstanceManager instanceManager)*`.

As Remy mentioned in the bugzilla provided, a (deprecated) method of `*public
static void releaseTag(Tag tag, InstanceManager instanceManager, boolean
reused)*` exists on 9.0.97 and onwards.
You should upgrade to a version >= 9.0.97 for your application.

Kind regards,
Dimitris

On Thu, Feb 6, 2025 at 3:48 PM Divyabharathi Sundaram
 wrote:

> Hi Dimitris,
>
> Noted, appreciate your advise on version 9.0.96.Below is the error and
> the application team have provided the reference link stating there is a
> bug in the version 9.0.96.
>
> Link:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=69386#c0
> 69386 – Pre-compiled JSPs result in NoSuchMethodError with latest upgrade<
> https://bz.apache.org/bugzilla/show_bug.cgi?id=69386#c0>
> There is no guarantee that previously generated code remains compatible
> with new Jasper runtime, this is untested and will remain that way. Also
> any fixes or optimizations occur in the generated code.
> bz.apache.org
>
> Messages:
>
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> javax.servlet.ServletException: java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> File: org/apache/jsp/multiselect_jsp.java
> Line number: 323
> Stacktraces
> org.apache.jasper.JasperException: javax.servlet.ServletException:
> java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:623)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:489)
>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:376)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:324)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:623)
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
>
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:641)
>
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:415)
>
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:347)
>
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:284)
>
> org.apache.struts2.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:164)
>
> org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResultSupport.java:186)
>
> com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:367)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:271)
>
> org.apache.struts2.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:256)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:100)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:100)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:138)
>
> com.opensymphony.xwork2.DefaultActionInvocation.i

Custom error page for invalid mutual authentication (TLS)

2025-02-06 Thread Peter Rader 
Hi,


I have a website that use mutual authentication for over 100 persons very
successfull since years.

Sometimes a client-certificate in the truststore of the server must be
deactivated, maybe the person died or his/her device got pinched.

As soon as the user access the website using a browser who has the client
certificate installed in the certificate-store of the browser, the website is
unavailable. Fair enougth! A generic website is displayed in the browser. For
firefox the message "SSL_ERROR_CERTIFICATE_UNKNOWN_ALERT" appears. Thats fair
and good.

However, is there a way to have a custom website instead of the browser's
built-in error-page?


Kind regards

Peter Rader
--
Fachinformatiker AE / IT Software Developer
Peter Rader
Wilsnacker Strasse 17
10559 Berlin - GERMANY
Tel: 0049 (0)30 / 6 29 33 29 6
Fax: 0049 (0)30 / 6 29 33 29 6
Handy: 0049 (0)176 / 87 521 576
Handy: 0049 (0)176 / 47 876 303

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Building tomcat-native on RHEL 8

2025-02-06 Thread Dimitris Soumis 
On Thu, Feb 6, 2025 at 7:30 PM Darryl Baker 
wrote:

> My question is why is tomcat-native dependent on APR at all? Could it be
> built without that dependency?
>
Tomcat Native relies on the Apache Portable Runtime (APR) to bridge the gap
between Tomcat, and native OS capabilities. APR provides APIs that map to
the OS. Tomcat Native is able to provide the performance increases due to
apr bypassing Java’s virtualized layer. So no, tomcat-native can not be
built without that dependency.

> Can I build tomcat native on Rocky Linux? Then could I use it on Red Hat?
> Has anyone tried that?
>
 The building process of tomcat native is OS agnostic. As long as the
required dependencies are provided to the building process, everything
should work flawlessly.
However, for the libraries produced in one system to work with another
system depends on factors such as the other system having equal various
library versions like glibc or OpenSSL, equal cpu architecture etc.

> Darryl Baker, GSEC, GCLD (he/him/his)
> Sr. System Administrator
> Distributed Application Platform Services
> Northwestern University
> 4th Floor
> 2020 Ridge Avenue
> Evanston, IL 60208-0801
> darryl.ba...@northwestern.edu 
> (847) 467-6674 
>
>
>
>
> On 2/6/25, 4:26 AM, "Dimitris Soumis"  dsou...@apache.org>> wrote:
>
>
> On Wed, Feb 5, 2025 at 7:58 PM Darryl Baker  >
> wrote:
>
>
> > I could if there was one. Red Hat stopped having Tomcat in the OS
> > distribution and is now part of the JBoss product the University decided
> > not to buy.
> >
> Tomcat is available in the OS distribution other than the Jboss web server
> product. Tomcat-native is not.
>
>
> > [root@XXX] tomcat-native-2.0.8-src]# yum search tomcat-native
> > Updating Subscription Management repositories.
> > No matches found.
> > [root@XXX] tomcat-native-2.0.8-src]#
> >
> > Darryl Baker, GSEC, GCLD (he/him/his)
> > Sr. System Administrator
> > Distributed Application Platform Services
> > Northwestern University
> >
> >
> >
> >
> > On 2/4/25, 4:21 PM, "Christopher Schultz"  
> > >> wrote:
> >
> >
> > Darryl,
> >
> >
> > On 2/3/25 1:17 PM, Darryl Baker wrote:
> > > Would someone please point me to the documentation on building
> > tomcat-native on RHEL 8 using the Red Hat supplied APR package?
> >
> >
> > Do you need to build from source, or can you use the RHEL binary?
> >
> >
> > $ sudo yum search tomcat-native
> > = Name Exactly Matched: tomcat-native =
> > tomcat-native.x86_64 : Tomcat native library
> >
> >
> > If you truly need to build, we can probably update the documentation to
> > indicate which popular packages would be necessary before building from
> > source.
> >
> >
> > -chris
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org  users-unsubscr...@tomcat.apache.org>  > users-unsubscr...@tomcat.apache.org  users-unsubscr...@tomcat.apache.org>>
> > For additional commands, e-mail: users-h...@tomcat.apache.org  users-h...@tomcat.apache.org>  > users-h...@tomcat.apache.org >
> >
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org  users-unsubscr...@tomcat.apache.org>
> > For additional commands, e-mail: users-h...@tomcat.apache.org  users-h...@tomcat.apache.org>
> >
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

Re: Release 10.1.35

2025-02-06 Thread Adrienne Farrell 
Hello

Sorry it took us a bit of time to setup the test scenario but I can
confirm that 10.1.35 has addressed the issue we were seeing in 10.1.33
and 10.1.34. We are confirming that the issue we are seeing is
resolved by the fix in 69527. Thank you very much for this fix!

Cheers,
Adrienne

On Tue, Feb 4, 2025 at 5:15 PM Christopher Schultz
 wrote:
>
> Adrienne and Mark,
>
> On 2/3/25 9:30 AM, Mark Thomas wrote:
> > On 03/02/2025 13:52, Adrienne Farrell wrote:
> >> Hello
> >>
> >> I am seeing https://bz.apache.org/bugzilla/show_bug.cgi?id=69527 in my
> >> Tomcat 10.1.33 and 10.1.34 and have to roll back to 10.1.31. I am just
> >> wondering when 10.1.35 might be released as I see the fix is in that
> >> update?
> >
> > If all goes to plan, the process should start later today. If not, it
> > will be the next few days.
>
> Apache Tomcat 10.1.35 release is ready for voting.
>
> Adrienne, if you'd care to try it out and reply to the VOTE thread on
> the development mailing list, I'd appreciate it.
>
> Thanks,
> -chris
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Building tomcat-native on RHEL 8

2025-02-06 Thread Darryl Baker 
My question is why is tomcat-native dependent on APR at all? Could it be built 
without that dependency? 

Can I build tomcat native on Rocky Linux? Then could I use it on Red Hat? Has 
anyone tried that?

Darryl Baker, GSEC, GCLD (he/him/his) 
Sr. System Administrator 
Distributed Application Platform Services 
Northwestern University 
4th Floor 
2020 Ridge Avenue 
Evanston, IL 60208-0801 
darryl.ba...@northwestern.edu  
(847) 467-6674  




On 2/6/25, 4:26 AM, "Dimitris Soumis" mailto:dsou...@apache.org>> wrote:


On Wed, Feb 5, 2025 at 7:58 PM Darryl Baker mailto:darryl.ba...@northwestern.edu>>
wrote:


> I could if there was one. Red Hat stopped having Tomcat in the OS
> distribution and is now part of the JBoss product the University decided
> not to buy.
>
Tomcat is available in the OS distribution other than the Jboss web server
product. Tomcat-native is not.


> [root@XXX] tomcat-native-2.0.8-src]# yum search tomcat-native
> Updating Subscription Management repositories.
> No matches found.
> [root@XXX] tomcat-native-2.0.8-src]#
>
> Darryl Baker, GSEC, GCLD (he/him/his)
> Sr. System Administrator
> Distributed Application Platform Services
> Northwestern University
>
>
>
>
> On 2/4/25, 4:21 PM, "Christopher Schultz"  
> >> 
> wrote:
>
>
> Darryl,
>
>
> On 2/3/25 1:17 PM, Darryl Baker wrote:
> > Would someone please point me to the documentation on building
> tomcat-native on RHEL 8 using the Red Hat supplied APR package?
>
>
> Do you need to build from source, or can you use the RHEL binary?
>
>
> $ sudo yum search tomcat-native
> = Name Exactly Matched: tomcat-native =
> tomcat-native.x86_64 : Tomcat native library
>
>
> If you truly need to build, we can probably update the documentation to
> indicate which popular packages would be necessary before building from
> source.
>
>
> -chris
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org 
>   users-unsubscr...@tomcat.apache.org 
> >
> For additional commands, e-mail: users-h...@tomcat.apache.org 
>   users-h...@tomcat.apache.org >
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org 
> 
> For additional commands, e-mail: users-h...@tomcat.apache.org 
> 
>




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Divyabharathi Sundaram 
Hi Dimitris,

We have recently upgraded to 9.0.96 for nearly 30 tomcat instances in which 
only two of the applications have reported issue. Can application code change 
helps in rectifying the issue or any other workaround or solution is available 
for the reported issue. Application code change may not be feasible as I am not 
sure how the team will take up, kindly let us know if any other alternate 
solution is available to the reported bug in the version 9.0.96 to avoid manual 
efforts in upgrading again.

Thanks & Regards,
S Divyabharathi

From: Divyabharathi Sundaram 
Sent: Thursday, February 6, 2025 11:27 PM
To: Tomcat Users List 
Subject: Re: REG: Version stability of Tomcat 9.0.96

Hi Dimitris,

Noted, Kindly hold the ticket we will get back after discussing with the 
application team.

Regards,

DivyaBharathi.S

TCS - Infra Midrange SME

Malaysia Airlines Berhad




From: Dimitris Soumis 
Sent: Thursday, February 6, 2025 10:31 PM
To: Tomcat Users List 
Subject: Re: REG: Version stability of Tomcat 9.0.96

CAUTION! This email originated from outside of MAG

Judging by the method call
JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/*Tag*
;Lorg/apache/tomcat/*InstanceManager*;*Z*) you are calling the method with
the 3 arguments of Tag, InstanceManager and boolean.

The only method definition in 9.0.96 is `*public static void releaseTag(Tag
tag, InstanceManager instanceManager)*`.

As Remy mentioned in the bugzilla provided, a (deprecated) method of `*public
static void releaseTag(Tag tag, InstanceManager instanceManager, boolean
reused)*` exists on 9.0.97 and onwards.
You should upgrade to a version >= 9.0.97 for your application.

Kind regards,
Dimitris

On Thu, Feb 6, 2025 at 3:48 PM Divyabharathi Sundaram
 wrote:

> Hi Dimitris,
>
> Noted, appreciate your advise on version 9.0.96.Below is the error and
> the application team have provided the reference link stating there is a
> bug in the version 9.0.96.
>
> Link:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=69386#c0
> 69386 – Pre-compiled JSPs result in NoSuchMethodError with latest upgrade<
> https://bz.apache.org/bugzilla/show_bug.cgi?id=69386#c0>
> There is no guarantee that previously generated code remains compatible
> with new Jasper runtime, this is untested and will remain that way. Also
> any fixes or optimizations occur in the generated code.
> bz.apache.org
>
> Messages:
>
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> javax.servlet.ServletException: java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> File: org/apache/jsp/multiselect_jsp.java
> Line number: 323
> Stacktraces
> org.apache.jasper.JasperException: javax.servlet.ServletException:
> java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:623)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:489)
>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:376)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:324)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:623)
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
>
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:641)
>
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:415)
>
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:347)
>
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:284)
>
> org.apache.struts2.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:164)
>
> org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResultSupport.java:186)
>
> com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:367)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:271)
>
> org.apache.struts2.interceptor.de

Tomcat 10.1 Upgrade & Uber JAR Error

2025-02-06 Thread Tim N 
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: REG: Version stability of Tomcat 9.0.96

2025-02-06 Thread Dimitris Soumis 
Judging by the method call
JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/*Tag*
;Lorg/apache/tomcat/*InstanceManager*;*Z*) you are calling the method with
the 3 arguments of Tag, InstanceManager and boolean.

The only method definition in 9.0.96 is `*public static void releaseTag(Tag
tag, InstanceManager instanceManager)*`.

As Remy mentioned in the bugzilla provided, a (deprecated) method of `*public
static void releaseTag(Tag tag, InstanceManager instanceManager, boolean
reused)*` exists on 9.0.97 and onwards.
You should upgrade to a version >= 9.0.97 for your application.

Kind regards,
Dimitris

On Thu, Feb 6, 2025 at 3:48 PM Divyabharathi Sundaram
 wrote:

> Hi Dimitris,
>
> Noted,  appreciate your advise on version 9.0.96.Below is the error and
> the application team have provided the reference link stating there is a
> bug in the version 9.0.96.
>
> Link:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=69386#c0
> 69386 – Pre-compiled JSPs result in NoSuchMethodError with latest upgrade<
> https://bz.apache.org/bugzilla/show_bug.cgi?id=69386#c0>
> There is no guarantee that previously generated code remains compatible
> with new Jasper runtime, this is untested and will remain that way. Also
> any fixes or optimizations occur in the generated code.
> bz.apache.org
>
> Messages:
>
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> javax.servlet.ServletException: java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
> File: org/apache/jsp/multiselect_jsp.java
> Line number: 323
> Stacktraces
> org.apache.jasper.JasperException: javax.servlet.ServletException:
> java.lang.NoSuchMethodError:
> org.apache.jasper.runtime.JspRuntimeLibrary.releaseTag(Ljavax/servlet/jsp/tagext/Tag;Lorg/apache/tomcat/InstanceManager;Z)V
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:623)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:489)
>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:376)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:324)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:623)
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
>
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:641)
>
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:415)
>
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:347)
>
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:284)
>
> org.apache.struts2.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:164)
>
> org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResultSupport.java:186)
>
> com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:367)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:271)
>
> org.apache.struts2.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:256)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:100)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:100)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:138)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:238)
>
> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
>
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
>
> com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:238)
>
> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.