Chaitanya,
On 6/5/24 09:11, Chaitanya Gopisetti wrote:
Also can you update on the End of life expected date for Tomcat 9.0.x version
-Original Message-
From: Christopher Schultz
Sent: Wednesday, June 5, 2024 6:37 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 9.0.xx JDK Version
Sent: Wednesday, June 5, 2024 6:37 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 9.0.xx JDK Version Support and EOL
Chaitanya,
On 6/5/24 08:47, Chaitanya Gopisetti wrote:
It was mentioned that Tomcat 9.0.x supports java 8 and later. So
wanted to know whether it supports Jdk 21? Also wanted to kno
Also can you update on the End of life expected date for Tomcat 9.0.x version
-Original Message-
From: Christopher Schultz
Sent: Wednesday, June 5, 2024 6:37 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 9.0.xx JDK Version Support and EOL
Chaitanya,
On 6/5/24 08:47, Chaitanya
Chaitanya,
On 6/5/24 08:47, Chaitanya Gopisetti wrote:
It was mentioned that Tomcat 9.0.x supports java 8 and later. So
wanted to know whether it supports Jdk 21? Also wanted to know the
End of life expected date for Tomcat 9.0.x version.
Tomcat 9 should run jut fine on any Java version from 8
Hi,
It was mentioned that Tomcat 9.0.x supports java 8 and later. So wanted to know
whether it supports Jdk 21?
Also wanted to know the End of life expected date for Tomcat 9.0.x version.
Regards,
Chaitanya
To the extent permitted by law, we may monitor electronic communications for
the purpos
Tomcat
> > 9.0.71 when developing. And since then, I get these "SEVERE" JSF error
> > messages (many of them) when I start Tomcat:
> >
> > SEVERE [main]
> >
> com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation
> > Unknow type constant pool
ed Eclipse to Version: 2023-09 (4.29.0) and
> at
> > the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat
> > 9.0.71 when developing. And since then, I get these "SEVERE" JSF error
> > messages (many of them) when I start Tomcat:
> >
(many of them) when I start Tomcat:
SEVERE [main]
com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation
Unknow type constant pool NN at position XX
Why is that? Could someone please give me a clue? I just upgraded Eclipse
and Tomcat, didn't do anything el
when I start Tomcat:
SEVERE [main]
com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation
Unknow type constant pool NN at position XX
Why is that? Could someone please give me a clue? I just upgraded Eclipse
and Tomcat, didn't do anything else relevant and now I get these messages.
And
On 13/11/2019 15:05, RICT (Ricco Truelsen) wrote:
> Hi
>
> Any official EOL on Tomcat 8.5.x yet?
> I can find official info on the Tomcat 8.0.x EOL, but not on the Tomcat 8.5.x?
No.
https://markmail.org/message/6wycxatwzwycmf43
Mark
-
Hi
Any official EOL on Tomcat 8.5.x yet?
I can find official info on the Tomcat 8.0.x EOL, but not on the Tomcat 8.5.x?
Best regards,
Ricco
On 08/02/17 00:57, James H. H. Lampert wrote:
Ladies and Gentlemen of the Tomcat List:
To date, the overwhelming bulk of our own Tomcat experience has been
under Java 6 JVMs. And we have a customer who will likely be losing that
JVM soon.
Are there any "gotchas" running 7.0.47 or later under Ja
Ladies and Gentlemen of the Tomcat List:
To date, the overwhelming bulk of our own Tomcat experience has been
under Java 6 JVMs. And we have a customer who will likely be losing that
JVM soon.
Are there any "gotchas" running 7.0.47 or later under Java 7?
--
James H. H. Lampert
Touchtone Corp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uzair,
On 2/9/16 1:11 PM, uzair rashid wrote:
> Most of our business is running Tomcat 7.x.xx or later. But, we
> have a business function of ours that is using Tomcat 5.0.xx.
> Unfortunately, this is causing a lot of issues in
Hello Experts:
Most of our business is running Tomcat 7.x.xx or later. But, we have a
business function of ours that is using Tomcat 5.0.xx. Unfortunately, this
is causing a lot of issues in terms of vulnerability remediation.
Apache Tomcat Servlet Host Manager Servlet Cross-Site Scripting
rom: Kiran Badi [mailto:ki...@poonam.org]
Sent: Tuesday, June 19, 2012 3:10 AM
To: Tomcat Users List
Subject: Protect JSP from Direct Access in Tomcat 7.0.xx
Hi All,
I need your guidance again.I have bunch of JSP's close to 100+ which I
need to protect it from direct access.
I have this mapping
mcat Users List
Subject: Protect JSP from Direct Access in Tomcat 7.0.xx
Hi All,
I need your guidance again.I have bunch of JSP's close to 100+ which I
need to protect it from direct access.
I have this mapping in web xml and this is not working,It seems that
probably i need to define a role
On 6/19/2012 10:22 AM, Tim Watts wrote:
Hopefully, you're trying to use or move toward the MVC (Model, View,
Controller) pattern. If not, you should. Google "MVC design pattern".
There are many, many frameworks that will make this easier for you (once
you learn them): Struts, Spring MVC...
If
On Tue, 2012-06-19 at 08:48 +0530, Kiran Badi wrote:
> No its not returning source code.I have couple of jsps where in I use EL
> in those to access session objects and directly accessing those jsps is
> not something I want.
Good move.
> >> 2. Is their any extra setting that is required if I
On 6/19/2012 8:03 AM, Tim Watts wrote:
Hi Kiran,
On Tue, 2012-06-19 at 05:40 +0530, Kiran Badi wrote:
Hi All,
I need your guidance again.I have bunch of JSP's close to 100+ which I
need to protect it from direct access.
By "direct access" do you mean that http://host/myapp/sample.jsp is
retu
Hi Kiran,
On Tue, 2012-06-19 at 05:40 +0530, Kiran Badi wrote:
> Hi All,
>
> I need your guidance again.I have bunch of JSP's close to 100+ which I
> need to protect it from direct access.
>
By "direct access" do you mean that http://host/myapp/sample.jsp is
returning the JSP source code rather
Hi All,
I need your guidance again.I have bunch of JSP's close to 100+ which I
need to protect it from direct access.
I have this mapping in web xml and this is not working,It seems that
probably i need to define a role first and then use below settings.But
unfortunately my app is open inter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sanjiv,
On 8/29/2011 8:53 AM, sanjivacharyya wrote:
> I have the below requirements for SSL certificates. Please do let
> me know is tomcat 6.xx supports below requirements :- 1) 128 bit
> data encryption will be employed. 2) 1024 b
Hi,
I have the below requirements for SSL certificates.
Please do let me know is tomcat 6.xx supports below requirements :-
1) 128 bit data encryption will be employed.
2) 1024 bit server certificate keys will be used.
3) 2048 bit VeriSign Intermediate and Root CA Certificate keys will be
pa.prabha...@do.treas.gov
To: users@tomcat.apache.org
Date: Thu, 20 Aug 2009 10:52:30 -0400
Subject: FW: Accessing Properties file located in Conf Directory of Tomcat 5.XX
_
From: Prabhakar, Kaverappa
Sent: Thursday, August 20, 2009 10:20 AM
To: 'use
I am assuming loader is an instance of a classloader. The classloader
doesn't see the conf directory. (But as your noticed - it does see the
common directory)
Your "easiest" (but tomcat specific) solution is to do something like this:
File confDir = new File(System.properties("catalina.home"),
le contenu fourni.
> From: kaverappa.prabha...@do.treas.gov
> To: users@tomcat.apache.org
> Date: Thu, 20 Aug 2009 10:52:30 -0400
> Subject: FW: Accessing Properties file located in Conf Directory of Tomcat
> 5.XX
>
>
>
> _
> From:
We have to place, as per rules set by the department, the properties file in
the Conf directory of Tomcat AS. The TOMCAT does not find the properties file
placed in CONF directory but it does find when placed in Common or Shared
directory of TOMCAT.
I tried placing the directory path in the jav
_
From: Prabhakar, Kaverappa
Sent: Thursday, August 20, 2009 10:20 AM
To: 'users@tomcat.apache.org'
Subject: Accessing Properties file located in Conf Directory of Tomcat 5.XX
We have to place, as per rules set by the department, the prope
nt="100" debug="0" connectionTimeout="2"
>>>>proxyPort="80" disableUploadTimeout="true" />
>>>>
>>>> and I've added the following to my httpd.conf:
>>>>
>>>>
It is just the port your Tomcat is running on, which could be any port,
so if you are using 8082 that will be your port... it's better though
not to be on port 80.
mip wrote:
Thanks Peter.
Should that be:
--
servers.conf
--
T1 tomcat.server.com:8082
ALL tomcat.ser
ProxyPass / http://foobar.com:8082/app/
>> ProxyPassReverse / http://foobar.com:8082/app/
>>
>>
>> The pages are being passed without any problems but the sessions are
>> being
>> lost as cookies are not being passed. I'm guessing I
Thats because your configuration is incomplete, in order for Apache to
pass the cookie to the correct context you need to do some additional
configuration (or alternatively use a connector like mod_jk)
You may need to configure the jvmRoute parameter in server.xml, this
allows Apache to map to
this message in context:
http://www.nabble.com/Tomcat-5.5%2C-Apache-2.0.XX-and-mod_proxy-tf4881521.html#a13970134
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomca
rahul
--
1. e4 _
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
A Sunley wrote:
> Is this bug with Tomcat 6, or is it intentional? The version 6 documentation
> mentions that setting useContextClassLoader switches between context and
> container class loading, but obviously that isn't the case anymore...
Ignore my previous post. It is indeed a bug in TC6.
Mar
D]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Problem-with-Tomcat-6.0.xx-and-JAAS-and-userContextClassLoader-tf4394188.html#a12534233
Sent f
A Sunley wrote:
> Is there anyway around this?
No.
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
F4BD60185FB0A1567A8F?page=history
According to the link it is because Tomcat 6 performs a Class.forName()
lookup.
Is there anyway around this?
Thanks,
Alan.
--
View this message in context:
http://www.nabble.com/Problem-with-Tomcat-6.0.xx-and-JAAS-and-userContextClassLoader-tf4394188.html#a1252
hing there :( and there is enough free space.
There is also
-XX:HeapDumpPath=DIRECTORY_OR_FILE
(Caution: I don't know, if all JVM versions that implement
-XX:+HeapDumpOnOutOfMemoryError, implement this one too).
You should check in the process table (if it's a unix like system) if
your
free space.
>
>
> > There is also
> >
> > -XX:HeapDumpPath=DIRECTORY_OR_FILE
> >
> > (Caution: I don't know, if all JVM versions that implement
> > -XX:+HeapDumpOnOutOfMemoryError, implement this one too).
> >
> > You should check in the process table (
; -XX:HeapDumpPath=DIRECTORY_OR_FILE
>
> (Caution: I don't know, if all JVM versions that implement
> -XX:+HeapDumpOnOutOfMemoryError, implement this one too).
>
> You should check in the process table (if it's a unix like system) if
> your switches are picked up appropriat
In the working directory of the process. Of course you need enough free
disk space.
There is also
-XX:HeapDumpPath=DIRECTORY_OR_FILE
(Caution: I don't know, if all JVM versions that implement
-XX:+HeapDumpOnOutOfMemoryError, implement this one too).
You should check in the process tabl
I specified that parameter in JAVA_OPTS variable, but after the first
"java.lang.OutOfMemoryError: Java heap space" error, no dump file was created.
Where should that file be created by default? any clue?
Thanks
--
Leggi GRATIS le tue mail con
> From: Gupta, Medhavi (GE Healthcare)
> [mailto:[EMAIL PROTECTED]
> Subject: Starting Tomcat 5.5.23 gives error in
> localhost.-xx-xx.log
>
> > I have tomcat 5.5.23 binary distribution Windows executable.
> >
> > java.lang.ClassFormatError: Ext
> Hi,
>
> I have tomcat 5.5.23 binary distribution Windows executable.
> Environmental variable JAVA_HOME is set to C:\Program
> Files\Java\jre1.5.0_06. When I try to start the Tomcat Service, I see
> the below error in localhost.-xx-xx.log file. I am not able to
> u
46 matches
Mail list logo
