> On 2025 Feb 11, at 19:21, Amit Pande wrote:
>
> Am planning to update the Tomcat configuration to support HTTP/2.
>
> Wanted to understand the difference between
>
> nested
> within the HTTP/1.1 connector
>
> Vs
>
> Supporting protocol=org.apache.coyote.http2.Http2Protocol in the conne
Hello,
Am planning to update the Tomcat configuration to support HTTP/2.
Wanted to understand the difference between
nested
within the HTTP/1.1 connector
Vs
Supporting protocol=org.apache.coyote.http2.Http2Protocol in the connector
configuration.
As I understand using the upgrade protocol
Note that I am experiencing this with Tomcat 9.0.99. So it seems the
recent point releases are all affected.
On Tue, Feb 11, 2025 at 12:56 PM David P. Caldwell
wrote:
>
> Also experiencing this with Java 17. but not Java 8, 11, or 21.
>
> Example run:
> https://github.com/davidpcaldwell/slime/ac
Also experiencing this with Java 17. but not Java 8, 11, or 21.
Example run:
https://github.com/davidpcaldwell/slime/actions/runs/13268650799/job/37043056764
- David.
On Tue, Feb 11, 2025 at 11:23 AM Daniel Skiles
wrote:
>
> I'm seeing the same thing in tomcat 10.1.35 with openjdk version "17.
I was able to work around it on 17.0.13 by adding --add-opens=java.base/
java.io=ALL-UNNAMED to my startup script.
On Tue, Feb 11, 2025 at 11:23 AM Daniel Skiles
wrote:
> I'm seeing the same thing in tomcat 10.1.35 with openjdk version "17.0.13"
> 2024-10-15
>
> On Tue, Feb 11, 2025 at 8:00 AM C
I'm seeing the same thing in tomcat 10.1.35 with openjdk version "17.0.13"
2024-10-15
On Tue, Feb 11, 2025 at 8:00 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Jack,
>
> On 2/11/25 5:56 AM, Jack Green wrote:
> > When you try to start `11.0.3` via:
> > ```
> > new Tomcat();
> >
Abirami,
On 2/10/25 6:14 AM, S Abirami wrote:
We are deploying webservices SOAP using embedded tomcat. It worked fine with JDK 8
& tomcat 10.
After upgrading to JDK 17 with tomcat 11, webservices generate source failed
first then I utilized Metrowebservices and Jax-ws related jars to solve the
opsie.. I suppose they can find a workaround for their solution
On Tue, Feb 11, 2025 at 8:55 PM Christopher Schultz
wrote:
>
> Jason,
>
> On 2/7/25 6:53 AM, Jason Wee wrote:
> > Why not use releaseTag with 2 arguments? That 3 arguments method is
> > deprecated in tomcat9.0.98 anyway...sooner
On 11/02/2025 12:42, Christopher Schultz wrote:
Mark,
On 2/7/25 3:42 AM, Mark Thomas wrote:
On 06/02/2025 19:25, Jalaj Asher wrote:
Hello,
Is it ok to delete files from tomcat/temp folder while the tomcat is
running ?
Generally, no. There are instances where that will break things.
It may
Jack,
On 2/11/25 5:56 AM, Jack Green wrote:
When you try to start `11.0.3` via:
```
new Tomcat();
```
An error is thrown:
```
Exception in thread "main" java.lang.ExceptionInInitializerError
at TomcatReproducer.main(TomcatReproducer.java:6)
Caused by: java.lang.reflect.InaccessibleObjec
Jason,
On 2/7/25 6:53 AM, Jason Wee wrote:
Why not use releaseTag with 2 arguments? That 3 arguments method is
deprecated in tomcat9.0.98 anyway...sooner it will be removed...
This isn't really an application issue. The application isn't calling
releaseTag() itself; the JSP compiler generated
Sebastian,
On 2/7/25 4:37 PM, Sebastian Trost wrote:
if updating your application is out of the question, I'm guessing that
there is no way to achieve this.
If updating your application is an option, you can set the clientAuth
attribute of your connector to 'want' instead of 'true' and then t
On Tue, Feb 11, 2025 at 1:41 PM Thomas Hoffmann (Speed4Trade GmbH)
wrote:
>
> Hello Ivano,
>
> it seems more like a decision from java side:
> https://snyk.io/de/blog/securitymanager-removed-java/
Indeed: https://openjdk.org/jeps/411
Tomcat is apparently one of the very few comprehensive securit
Mark,
On 2/7/25 3:42 AM, Mark Thomas wrote:
On 06/02/2025 19:25, Jalaj Asher wrote:
Hello,
Is it ok to delete files from tomcat/temp folder while the tomcat is
running ?
Generally, no. There are instances where that will break things.
It may be possible to delete some files safely - althou
Hello Ivano,
it seems more like a decision from java side:
https://snyk.io/de/blog/securitymanager-removed-java/
> -Ursprüngliche Nachricht-
> Von: Ivano Luberti
> Gesendet: Dienstag, 11. Februar 2025 13:33
> An: users@tomcat.apache.org
> Betreff: Re: catalina.policy file not available
Hi Mark, any link to read the reason of this decision?
Il 11-Feb-25 13:03, Mark Thomas ha scritto:
On 11/02/2025 10:53, S Abirami wrote:
Hi All,
Tomcat catalina.policy file is not available from Tomcat 11.0.0.
Is there any specific reason for the removal?
Support for running under a Securit
On 11/02/2025 10:53, S Abirami wrote:
Hi All,
Tomcat catalina.policy file is not available from Tomcat 11.0.0.
Is there any specific reason for the removal?
Support for running under a SecurityManager has been removed.
Mark
---
When you try to start `11.0.3` via:
```
new Tomcat();
```
An error is thrown:
```
Exception in thread "main" java.lang.ExceptionInInitializerError
at TomcatReproducer.main(TomcatReproducer.java:6)
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field
static final
Hi All,
Tomcat catalina.policy file is not available from Tomcat 11.0.0.
Is there any specific reason for the removal?
Regards,
Abirami.S
19 matches
Mail list logo
