Your application must not package any of the specification API jars
provided by Tomcat. That includes annotation-api.jar
Tomcat implements the specific version of the API defined by those jars.
You can't drop in a different API version and expect Tomcat to magically
implement that new version
This makes no sense.
The application and the container need to be able to maintain an
independent life cycle of the libraries. I may want to update Tomcat and
not be concerned that it breaks my application because I may not even have
means to adapt the application to the updated tomcat library ver
This is another reason why separating CATALINA_HOME from CATALINA_BASE is a
good thing.
Dream * Excel * Explore * Inspire
Jon McAlexander
Infrastructure Engineer
Asst Vice President
He/His
Middleware Product Engineering
Enterprise CIO | EAS | Middleware | Infrastructure Solutions
8080 Cobblesto
Clay,
On 4/5/22 12:47, Clay Lehman wrote:
Hello!
I am trying to set up Tomcat Native using OpenSSL v3.0.2, and running into
an error on startup. I have tried a ton of things, searched, read the docs
over and over, and cannot get past this. Has anyone had success with this
setup?
I created
Joel,
On 4/5/22 10:33, Joel Griffith wrote:
I'm running a webapp under Tomcat 9 on Ubuntu 20.04. We run Tomcat as an
ad-hoc system user who owns the Tomcat installation files.
On Friday, the app stopped working. Over the weekend, I determined that
the problem was that something had reset the
5 Apr 2022 20:58:26 Cherio :
I found what the issue is. This has to do with the sequence of loading
of
libraries/jars AND project supplied "annotation-api.jar" which declares
PostConstruct annotation. The same set of annotations are also being
supplied by Tomcat in an identically named JAR. S
> -Ursprüngliche Nachricht-
> Von: Cherio
> Gesendet: Dienstag, 5. April 2022 17:17
> An: Tomcat Users List
> Betreff: Re: PostConstruct annotation in a filter since version 9.0.60
>
> I did ran the diffs between versions. With my naked eye I didn't spot
> anything obvious that in my m
I found what the issue is. This has to do with the sequence of loading of
libraries/jars AND project supplied "annotation-api.jar" which declares
PostConstruct annotation. The same set of annotations are also being
supplied by Tomcat in an identically named JAR. Sometime during java/Tomcat
startup
Robert, Brian,
On 4/5/22 13:59, Robert Turner wrote:
I think you need to use an ARM-based JVM -- IIRC, you will need Corretto
JDK 18 I think, otherwise it will be running in emulation.
+1
M1 macs can run either x86_84 code OR arm64, but not both in the same
process.
If you want to run tcna
Harri,
On 4/5/22 13:29, Harri Pesonen wrote:
Ok, it is a bit disappointing that Tomcat does not support this in
standard webapps folder.
But I found an easy workaround: create Windows junction app#latest
that points to app#1 folder (both in webapps).
You are doing something which is definitel
I think you need to use an ARM-based JVM -- IIRC, you will need Corretto
JDK 18 I think, otherwise it will be running in emulation.
On Tue, Apr 5, 2022 at 1:56 PM Paquin, Brian wrote:
> After compiling Tomcat Native (that comes with Tomcat 9.0.62, version
> 1.2.32) on a (ARM) M1 Mac (with Amazon
After compiling Tomcat Native (that comes with Tomcat 9.0.62, version 1.2.32)
on a (ARM) M1 Mac (with Amazon Coretto 11 JDK, APR, and OpenSSL 1.1.1n), I get
the following error in Catalina.out:
05-Apr-2022 11:10:32.307 WARNING [main]
org.apache.catalina.core.AprLifecycleListener.init The Apache
Ok, it is a bit disappointing that Tomcat does not support this in standard
webapps folder.
But I found an easy workaround: create Windows junction app#latest that points
to app#1 folder (both in webapps).
-Harri
-Original Message-
From: Mark Thomas
Sent: perjantai 1. huhtikuuta 2022
Hello!
I am trying to set up Tomcat Native using OpenSSL v3.0.2, and running into
an error on startup. I have tried a ton of things, searched, read the docs
over and over, and cannot get past this. Has anyone had success with this
setup?
I created a fully working sample project and Dockerfile
I did ran the diffs between versions. With my naked eye I didn't spot
anything obvious that in my mind would be directly related to this behavior
change.
At the same time, when I toggle between the above mentioned Tomcat versions
the exact same application either starts successfully or fails on
Po
On Tue, Apr 5, 2022 at 4:02 PM Cherio wrote:
>
> Yes, I confirm. For this project I download Tomcat from here:
> https://archive.apache.org/dist/tomcat/tomcat-$MAJOR_VER/v$VER/bin/apache-tomcat-$VER.tar.gz
>
> BTW @PostConstruct doesn't have to do with dependency injection. It is
> about lifecycle
Hi,
I'm running a webapp under Tomcat 9 on Ubuntu 20.04. We run Tomcat as an
ad-hoc system user who owns the Tomcat installation files.
On Friday, the app stopped working. Over the weekend, I determined that
the problem was that something had reset the ownership of the Tomcat
installation files
I forgot to mention that the Tomcat stack trace I posted earlier is from
Tomcat 9.0.62. The change in behavior was observed starting Tomcat 9.0.60
On Tue, Apr 5, 2022 at 10:01 AM Cherio wrote:
> Yes, I confirm. For this project I download Tomcat from here:
>
> https://archive.apache.org/dist/to
Yes, I confirm. For this project I download Tomcat from here:
https://archive.apache.org/dist/tomcat/tomcat-$MAJOR_VER/v$VER/bin/apache-tomcat-$VER.tar.gz
BTW @PostConstruct doesn't have to do with dependency injection. It is
about lifecycle processing.
The change in behavior was narrowed down to
19 matches
Mail list logo
