Re: Tomcat 9.0.xx JDK Version Support and EOL

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

Re: Tomcat 9.0.xx JDK Version Support and EOL

: 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 know

RE: Tomcat 9.0.xx JDK Version Support and EOL

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

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 know the End of life expected date for Tomcat 9.0.x version. Tomcat 9 should run jut fine on any Java version from

Tomcat 9.0.xx JDK Version Support and EOL

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

Re: Compile with JDK 17, run on JRE 11?

, 2024 at 11:02 PM Troels Arvin wrote: > Hello, > > Since 9.0.83, building Tomcat has required JDK 17, according to the > release notes. > > Is it possible to take the resulting binaries and run them on JRE 11? > > -- > Regards, > Troels Arvin >

Re: Compile with JDK 17, run on JRE 11?

On 17/02/2024 16:01, Troels Arvin wrote: Hello, Since 9.0.83, building Tomcat has required JDK 17, according to the release notes. Is it possible to take the resulting binaries and run them on JRE 11? Yes. The minimum Java version at runtime (8) is unchanged. Mark

Compile with JDK 17, run on JRE 11?

Hello, Since 9.0.83, building Tomcat has required JDK 17, according to the release notes. Is it possible to take the resulting binaries and run them on JRE 11? -- Regards, Troels Arvin

Re: Cannot start java issue after Tomcat9 and JDK 11 updates

on procrun finished. > > > > > > My CLASSPATH="C:\Tomcat\bin\bootstrap.jar;C:\Tomcat\bin\tomcat-juli.jar" > > bootstrap.jar is present in Tomcat\bin, and the folder permissions for > > Tomcat mirror what is specified on another, working, server (Tomc

Re: Cannot start java issue after Tomcat9 and JDK 11 updates

uot;C:\Tomcat\bin\bootstrap.jar;C:\Tomcat\bin\tomcat-juli.jar" bootstrap.jar is present in Tomcat\bin, and the folder permissions for Tomcat mirror what is specified on another, working, server (Tomcat 9.0.62 with jdk and jre 1.8.0_331) I've searched the mail archives and online, and fou

Cannot start java issue after Tomcat9 and JDK 11 updates

i.jar" bootstrap.jar is present in Tomcat\bin, and the folder permissions for Tomcat mirror what is specified on another, working, server (Tomcat 9.0.62 with jdk and jre 1.8.0_331) I've searched the mail archives and online, and found similar questions, but those solutions have not resolved

Re: Ciphers Warning in logfile for Tomcat 8.5.96 (with Adoptium jdk-8.0.392.8-hotspot)

Using embedded Tomcat, therefore no catalina.bat Markus Am Fr., 1. Dez. 2023 um 15:42 Uhr schrieb Mark Thomas : > On 01/12/2023 14:29, Markus Schlegel wrote: > > Hi Peter, > > Thank you for your hint about "-Djdk.tls.ephemeralDHKeySize=2048". > > I indeed did not knew that this option exists.

Re: Ciphers Warning in logfile for Tomcat 8.5.96 (with Adoptium jdk-8.0.392.8-hotspot)

On 01/12/2023 14:29, Markus Schlegel wrote: Hi Peter, Thank you for your hint about "-Djdk.tls.ephemeralDHKeySize=2048". I indeed did not knew that this option exists. When I enable it, I get Grad "A" from SSLLabs while it still lists 8 weak ciphers out of 12. Because I get to grade "A" with

Re: Ciphers Warning in logfile for Tomcat 8.5.96 (with Adoptium jdk-8.0.392.8-hotspot)

Hi Peter, Thank you for your hint about "-Djdk.tls.ephemeralDHKeySize=2048". I indeed did not knew that this option exists. When I enable it, I get Grad "A" from SSLLabs while it still lists 8 weak ciphers out of 12. Because I get to grade "A" with this setting, I can indeed use the default

Re: Ciphers Warning in logfile for Tomcat 8.5.96 (with Adoptium jdk-8.0.392.8-hotspot)

Hi > Am 29.11.2023 um 11:46 schrieb Markus Schlegel : > > Hi, > This is a continuation of the discussion taken below > https://bz.apache.org/bugzilla/show_bug.cgi?id=67628 where I asked about > the following warning which appears in our log: > > (29.11.2023 09:53:14

Re: Ciphers Warning in logfile for Tomcat 8.5.96 (with Adoptium jdk-8.0.392.8-hotspot)

On 29/11/2023 10:46, Markus Schlegel wrote: Changing the config to add ":-CBC" to the default config as suggested by Mark in bugzilla does not have any effect. Still Grade B, 10 weak out of 12. It seems to me that -CBC might not be a valid option at all? Mark got different results when he

Ciphers Warning in logfile for Tomcat 8.5.96 (with Adoptium jdk-8.0.392.8-hotspot)

Hi, This is a continuation of the discussion taken below https://bz.apache.org/bugzilla/show_bug.cgi?id=67628 where I asked about the following warning which appears in our log: (29.11.2023 09:53:14 org.apache.tomcat.util.net.SSLUtilBase getEnabled WARNING T-19): Tomcat interprets the [ciphers]

Re: Autocommit issue with JDK 1.8, Tomcat 9.0.60, ojdbc8.jar and Oracle DB 19c (19.14.0.0)

Please DO NOT cross-post questions to both the users list and the dev list. Questions like this belong on the users list. On 15/02/2023 06:32, Promit Banik wrote: Hello everyone, Recently we have done an environment setup upgradation/migration as mentioned below for our application: JDK 1.7

Autocommit issue with JDK 1.8, Tomcat 9.0.60, ojdbc8.jar and Oracle DB 19c (19.14.0.0)

Hello everyone, Recently we have done an environment setup upgradation/migration as mentioned below for our application: JDK 1.7 ---> JDK 1.8 Tomcat 7.0.47 ---> Tomcat 9.0.60 (Also using Apache HTTP Server along with Apache Tomcat for new setup) ojdbc7.jar ---> ojdbc8.jar Oracle 12c (1

RE: Tomcat service switches to another JDK under the hood

I have some updates. First of all, there is no JDK switch under the hood. I am glad my conclusion was wrong. In my REST API client app I use Java 11+ HTTPClient. For the POST call the external API requires Content-Lenght header even the body is empty, which HTTPClient doesn't support out

Re: Tomcat service switches to another JDK under the hood

Nothing you mentioned could have any effect. How do you ensure jdks are not mixing between tomcat and the other jdk8 application? Try to use separated cmd files as described above for both Tomcat and the other application and remove all jdk configurations from windows variables just to test

RE: Tomcat service switches to another JDK under the hood

There isn't any sign of the tomcat restart in the tomcat logs. In tomcat9-stderr-2022-04-08.log there is just one bootstrap section with the path to JDK 17, followed by mesages about the registering webapps. Then weekend of silence interrupted by today's exception. In that bootstrap section

Re: Tomcat service switches to another JDK under the hood

Tosovsky wrote: > We have a mixed JDK environment on our internal Windows Server. > > Tomcat is installed using the service installer and its service > configuration points to the JDK 17 as it serves some internal apps > requiring > JDK 12+. > > > > JAVA_HOME p

Tomcat service switches to another JDK under the hood

We have a mixed JDK environment on our internal Windows Server. Tomcat is installed using the service installer and its service configuration points to the JDK 17 as it serves some internal apps requiring JDK 12+. JAVA_HOME points to older JDK 8. PATH variable contains link to JDK 8

RE: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

Thomas > Sent: Monday, August 23, 2021 3:06 AM > To: users@tomcat.apache.org > Subject: Re: clearReferencesThreads issues warning about 2 threads, > spawned by JDK in printing components > > On 23/08/2021 08:10, Thomas Hoffmann (Speed4Trade GmbH) wrote: > > > > >

Re: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

should be ignored when checking for orphaned threads? No, for the same reason. It was tested with Tomcat 9.0.52, Windows 10, Coretto-JDK 11.0.12_7. You might want to consider raising a bug against the JDK. It could be argued that those threads should be created with a specific class loader

AW: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

omcat 9.0.52, Windows 10, Coretto-JDK 11.0.12_7. You might want to consider raising a bug against the JDK. It could be argued that those threads should be created with a specific class loader to avoid memory leaks in container environments. Mark Great, I will test this out and change the

Re: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

threads? No, for the same reason. It was tested with Tomcat 9.0.52, Windows 10, Coretto-JDK 11.0.12_7. You might want to consider raising a bug against the JDK. It could be argued that those threads should be created with a specific class loader to avoid memory leaks in container environments

clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

, patts); This triggers the JDK to spawn two threads, which can be seen in the OpenJDK-Sources: https://github.com/AdoptOpenJDK/openjdk-jdk11/blob/master/src/java.desktop/windows/classes/sun/print/PrintServiceLookupProvider.java (see around line no 134 ff) --> Thread thr = new Thread(null,

Re: Updating Oracle JDK or JRE from 1.8.0-1.8.0_291 to 1.8.0-1.8.0_301, Breaks Apache Tomcat 9 Connector Http11AprProtocol

>>Apache Tomcat 9.0.50 (Also issue with 9.0.44) >>Oracle JDK and JRE 1.8.0-1.8.0_301 >>Red Hat Enterprise Linux Server release 7.9 >>When updating JDK/JRE from build 1.8.0_291-b10 to 1.8.0_301-b09, Apache >>Tomcat Connector (org.apache.coyote.http11.Htt

Re: Updating Oracle JDK or JRE from 1.8.0-1.8.0_291 to 1.8.0-1.8.0_301, Breaks Apache Tomcat 9 Connector Http11AprProtocol

https://bugs.openjdk.java.net/browse/JDK-8202837 https://www.oracle.com/java/technologies/javase/8u301-bugfixes.html What now? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users

Updating Oracle JDK or JRE from 1.8.0-1.8.0_291 to 1.8.0-1.8.0_301, Breaks Apache Tomcat 9 Connector Http11AprProtocol

Apache Tomcat 9.0.50 (Also issue with 9.0.44) Oracle JDK and JRE 1.8.0-1.8.0_301 Red Hat Enterprise Linux Server release 7.9 When updating JDK/JRE from build 1.8.0_291-b10 to 1.8.0_301-b09, Apache Tomcat Connector (org.apache.coyote.http11.Http11AprProtocol) failed to load server key

Re: Tomcat 9.0.36 - JDK 13/14

On 02.07.2020 10:23, Utkarsh Bhargav wrote: Please i have resolved my issue Kindly stop sending mails Hi. You receive these emails because you subscribed to the email list "users@tomcat.apache.org". To not receive these emails anymore, you should unsubscribe from the list, be sending an

Re: Tomcat 9.0.36 - JDK 13/14

ion might have messed up, so had to create a > sample war file to check this. > > Anyone can try this and see if it works for them. Just build a simple > spring boot app with jdk 13/14 and deploy it on the latest tomcat running > on jdk 1.8. Maybe something is messed up in my environm

Re: Tomcat 9.0.36 - JDK 13/14

. Just build a simple spring boot app with jdk 13/14 and deploy it on the latest tomcat running on jdk 1.8. Maybe something is messed up in my environment. Here is console catalina.out log along with same use case classes from spring site. 29-Jun-2020 20:19:24.852 INFO [main

Re: Tomcat 9.0.36 - JDK 13/14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kiran, On 6/26/20 22:01, Kiran Badi wrote: > we fixed the issue Mark. > > Actually tomcat was running on JDK 1.8 and applications were built > using JDK 13/14.So when they were deployed to tomcat running with > 1.8, they were givi

Re: Tomcat 9.0.36 - JDK 13/14

we fixed the issue Mark. Actually tomcat was running on JDK 1.8 and applications were built using JDK 13/14.So when they were deployed to tomcat running with 1.8, they were giving 404. Now plan is to explore and upgrade tomcat to at least jdk 13. It would have been nice really to have at least

Re: Tomcat 9.0.36 - JDK 13/14

On 26/06/2020 05:45, Kiran Badi wrote: > Hi All, > > I wanted to check if tomcat 9.0.36 supports open jdk 13/14. Supported Java versions are listed at: http://tomcat.apache.org/whichversion.html "Java 8 and later" includes Java 13 and Java 14. > I created a simpl

Tomcat 9.0.36 - JDK 13/14

Hi All, I wanted to check if tomcat 9.0.36 supports open jdk 13/14. I created a simple spring boot war file and compiled/built it with openjdk 13/14. After running maven install , I deployed the war file from the target directory to tomcat webapps using tomcat manager. It did not work and gave

Re: Many memberDisappeared messages logged in cluster (with 1-cpu nodes) using JDK 12 & above

On 28/04/2020 06:42, Mahathi Vavilala wrote: > Hi, > > For default values of frequency (=500) and dropTime (=3000) in cluster > installation with TOMEE 7.0.7 (uses Tomcat 8.5.50.0) using JDK 12 or above > only, many memberDisappeared messages are logged on all nodes of the &g

Many memberDisappeared messages logged in cluster (with 1-cpu nodes) using JDK 12 & above

Hi, For default values of frequency (=500) and dropTime (=3000) in cluster installation with TOMEE 7.0.7 (uses Tomcat 8.5.50.0) using JDK 12 or above only, many memberDisappeared messages are logged on all nodes of the cluster (almost for every 2 minutes). This is occuring even when the system

Re: Support for JDK only by Windows Installer?

e >> account of that yet. > > The environment variable JAVA_HOME isn't supported actually. > > I added this as the last check after JRE64/32, JRE in JDK, now new JDK > only and then environment variable. > > We can discus to use environment variable first of all? I think thi

Re: Support for JDK only by Windows Installer?

producible description of the issue (in Bugzilla). What JDK are you using, from what vendor, and what are the steps to reproduce the issue. > But because of getting no error code and finding no log-file after a failed > silent installation. Generally, 1) Without a JDK the installer ca

Re: Support for JDK only by Windows Installer?

added this as the last check after JRE64/32, JRE in JDK, now new JDK only and then environment variable. We can discus to use environment variable first of all? I think this could be more common? Alexander - To unsubscribe, e

Re: Support for JDK only by Windows Installer?

Am 15.11.2019 22:23, schrieb Mark Thomas: Patches welcome. Mark A patch is nearly ready. I will sent a pull request asap. Alexander - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands,

Re: Support for JDK only by Windows Installer?

On 15/11/2019 15:50, Alexander Norz wrote: > Hello, > > is there a good point why the Windows Service Installer > (apache-tomcat-9.0.27.exe) did not support Oracles Java JDK (11 without > JRE) out-of-the-box especially for silent installation? Because Oracle changed the d

Support for JDK only by Windows Installer?

Hello, is there a good point why the Windows Service Installer (apache-tomcat-9.0.27.exe) did not support Oracles Java JDK (11 without JRE) out-of-the-box especially for silent installation? Meanwhile I know that I have to add a config-file with parameter /C for silent installation

Re: TOMCAT 7.0.92 with JDK 11 :- ERROR localhost-startStop-1 org.apache.catalina.startup.ContextConfig - Unable to process Jar tools.jar for annotations

b application running on Tomcat server container. Web > > application is compiled and using JDK 11 as runtime JRE for execution > > purpose. > > > > Tomcat Version : - 7.0.92 > > JDK Version :- 11 > > The stack trace below is not consistent with the versio

Re: TOMCAT 7.0.92 with JDK 11 :- ERROR localhost-startStop-1 org.apache.catalina.startup.ContextConfig - Unable to process Jar tools.jar for annotations

On 09/01/2019 09:19, Ravi Kumar wrote: > Dear Team, > > We have a web application running on Tomcat server container. Web > application is compiled and using JDK 11 as runtime JRE for execution > purpose. > > Tomcat Version : - 7.0.92 > JDK Version :- 1

TOMCAT 7.0.92 with JDK 11 :- ERROR localhost-startStop-1 org.apache.catalina.startup.ContextConfig - Unable to process Jar tools.jar for annotations

Dear Team, We have a web application running on Tomcat server container. Web application is compiled and using JDK 11 as runtime JRE for execution purpose. Tomcat Version : - 7.0.92 JDK Version :- 11 Problem Description :- 1.We are seeing the errors in tomcat log regarding jar scanning

Re: How to update new JDK version in apache-tomcat-7.0.84 windows service

On 4/18/2018 10:18 AM, Somu Sundar Reddy.Y wrote: > Hi,  Recently I installed Tomcat windows service using > apache-tomcat-7.0.84.exe  installation file and during installation, I was > using JDK 1.8 Update 162 in my computer.  With this installation file , > windows service is a

Re: How to update new JDK version in apache-tomcat-7.0.84 windows service

On 18/04/18 17:18, Somu Sundar Reddy.Y wrote: > Hi,  Recently I installed Tomcat windows service using > apache-tomcat-7.0.84.exe  installation file and during installation, I was > using JDK 1.8 Update 162 in my computer.  With this installation file , > windows service is a

How to update new JDK version in apache-tomcat-7.0.84 windows service

Hi,  Recently I installed Tomcat windows service using apache-tomcat-7.0.84.exe  installation file and during installation, I was using JDK 1.8 Update 162 in my computer.  With this installation file , windows service is automatically created and am able to start and stop the service without

Re: Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

nContext.java?r1=1636341=1642698> by markt? -- View this message in context: http://tomcat.10.x6.nabble.com/Problem-with-get-ROOT-context-in-servlet-on-tomcat-8-0-30-jdk-1-7-0-79-tp509p5063440.html Sent from the Tomcat - User mailing list archi

Re: Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

viewvc/tomcat/tc8.0.x/trunk/java/org/apache/catalina/core/ApplicationContext.java?r1=1636341=1642698> by markt? -- View this message in context: http://tomcat.10.x6.nabble.com/Problem-with-get-ROOT-context-in-servlet-on-tomcat-8-0-30-jdk-1-7-0-79-tp509p5063440.html Sent from the Tomca

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

Dezember 2016 22:36 An: Tomcat Users List >> <users@tomcat.apache.org> Betreff: Re: Tomcat Version 7.0.34 + >> jdk 1.6 is not supporting TLS Protocol TLS1.2 >> > Frank, > > On 12/15/16 10:19 AM, frank.pien...@materna.de wrote: >>>> Q1 use recent java8 Versi

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

<users@tomcat.apache.org> > Betreff: Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS > Protocol TLS1.2 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Frank, > > On 12/15/16 10:19 AM, frank.pien...@materna.de wrote: > > Q1 use recent j

AW: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

This was a typo, no plans for tls 1.3 in java yet -Ursprüngliche Nachricht- Von: Christopher Schultz [mailto:ch...@christopherschultz.net] Gesendet: Donnerstag, 15. Dezember 2016 22:36 An: Tomcat Users List <users@tomcat.apache.org> Betreff: Re: Tomcat Version 7.0.34 + j

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank, On 12/15/16 10:19 AM, frank.pien...@materna.de wrote: > Q1 use recent java8 Version if you want secure TLS 1.3 choose > right cipher. That might have been a typo, but I wanted to be clear that Java 8 doesn't support TLSv1.3. TLSv1.3 is

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dhanesh, On 12/15/16 8:29 AM, dhanesh1212121212 wrote: > Hi Team, > > *Requirement:* > > Support for PROTOCOL TLSv1.2. > > We are currently using Tomcat Version 7.0.34 + jdk 1.6 and this is > not supporting TLS Protocol

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

=DgIFAg=9qXE_JLypiubC-9T_PAPwg=Xhx3wY6yyvp3Qb9jYE01li0hTn39VkdJ0f9dlbDc57Y=Xrdrm6GVqFwIoc_CKnTdYIIAsjL2s5HVajfxaWvZkvU=6nGWeTS-AZoQeyKqTiC6iHB_qCDZa0q79bz0jn0rCeQ= > ", > >will Tomcat Version 7.0.34 support jdk 1.8? > > > >Question 2. Which is the best approach

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

HVajfxaWvZkvU=6nGWeTS-AZoQeyKqTiC6iHB_qCDZa0q79bz0jn0rCeQ= ", will Tomcat Version 7.0.34 support jdk 1.8? Question 2. Which is the best approach Tomcat Version 7.0.34 + jdk 1.7 or jdk 1.8? Question 3. Do we need to upgrade Tomcat version to new one, if yes then

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

need to choose. Refereed the Tomcat Site "http://tomcat.apache.org/whichversion.html;, will Tomcat Version 7.0.34 support jdk 1.8? Question 2. Which is the best approach Tomcat Version 7.0.34 + jdk 1.7 or jdk 1.8? Question 3. Do we need to upgrade Tomcat version to new one, if yes then

Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

Hi Team, *Requirement:* Support for PROTOCOL TLSv1.2. We are currently using Tomcat Version 7.0.34 + jdk 1.6 and this is not supporting TLS Protocol TLS1.2. Please let us know what are the steps we need to take to have support of TLS1.2 in Tomcat Version 7.0.34. Posting few questions along

Re: tomcat 7.0.54 /jdk 1.8 - only TLS_RSA_* ciphers work

On 01/11/2016 20:40, Christopher Schultz wrote: > Daba, > > On 11/1/16 4:33 PM, capt.spock wrote: >> Stumped with this issue...environment tomcat 7.054 with openjdk >> version "1.8.0_111" OpenJDK Runtime Environment (build >> 1.8.0_111-b15) > >> Couple of servers with below config in server.xml

Re: tomcat 7.0.54 /jdk 1.8 - only TLS_RSA_* ciphers work

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Daba, On 11/1/16 4:33 PM, capt.spock wrote: > Stumped with this issue...environment tomcat 7.054 with openjdk > version "1.8.0_111" OpenJDK Runtime Environment (build > 1.8.0_111-b15) > > Couple of servers with below config in server.xml throws

tomcat 7.0.54 /jdk 1.8 - only TLS_RSA_* ciphers work

Stumped with this issue...environment tomcat 7.054 with openjdk version "1.8.0_111" OpenJDK Runtime Environment (build 1.8.0_111-b15) Couple of servers with below config in server.xml throws warning in Catalina and browsers have issue connecting. INFO: The APR based Apache Tomcat Native

Re: Housing and reading internal resources using Tomcat 8.5.4 and JDK 1.8

Hi Chris, Thank you for the responses, yes those both help. I did a lot of reading yesterday and was unable to get a clear answer at how this should be done with JEE, where internal resource files are expected to reside (besides just generally being under WEB-INF) within the deployment, and the

Re: Housing and reading internal resources using Tomcat 8.5.4 and JDK 1.8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Doug, On 8/29/16 6:29 PM, Doug Gschwind wrote: > Hello everyone, > > I have a file xyz.txt that is specific to my web application which > needs to be located by my web application, and I wish to find that > resource via

Re: Housing and reading internal resources using Tomcat 8.5.4 and JDK 1.8

> Hello everyone, > > I have a file xyz.txt that is specific to my web application which needs to > be located by my web application, and I wish to find that resource via > getClass().ClassLoader().getResource("xyz.txt") at runtime. The xyz.txt > file has no relation to any particular Java class

Housing and reading internal resources using Tomcat 8.5.4 and JDK 1.8

Hello everyone, I have a file xyz.txt that is specific to my web application which needs to be located by my web application, and I wish to find that resource via getClass().ClassLoader().getResource("xyz.txt") at runtime. The xyz.txt file has no relation to any particular Java class in our

Re: Custom Authentication in Tomcat 8.5.4 using JDK 1.8.0_92?

Hi Mark, Very good, thank you for that direction. Both approaches you suggest seem appropriate, but I was unable to find any guide that describes how to provide/implement a JASPIC module, let alone that within Tomcat. I am hoping a custom Authenticator via extending AuthenticatorBase

Re: Custom Authentication in Tomcat 8.5.4 using JDK 1.8.0_92?

On 26/08/2016 06:54, Doug Gschwind wrote: > Hello, > In my research today on the topic, this appears to be much more difficult > than I would expect in Tomcat 8.5, so I can only conclude I am missing > something. Here are the two potential solutions I have found : > > 1) Provide our own

Custom Authentication in Tomcat 8.5.4 using JDK 1.8.0_92?

Hello, I am attempting to migrate our web app from Resin 3.1 to Tomcat 8.5.4. Ultimately, the intent is to be able to run our web app within Tomcat 8.5 on MAC OS X (in dev mode) or on a CentOS 7 box for production. With Resin 3.1, you can use a subclass of the Resin AbstractAuthenticator class

Re: Tomcat 7 on JDK 6 or JDK 7

Thank you David!! -Gokul On Thu, Jun 2, 2016 at 6:16 AM, David kerber <dcker...@verizon.net> wrote: > On 6/2/2016 6:50 AM, Gokul wrote: > >> Hello, >> >> I am running tomcat 7.0.65. >> >> Currently the tomcat is running on JDK 1.6. Can someone ple

Re: Tomcat 7 on JDK 6 or JDK 7

On 6/2/2016 6:50 AM, Gokul wrote: Hello, I am running tomcat 7.0.65. Currently the tomcat is running on JDK 1.6. Can someone please confirm if there is any performance impact if tomcat 7 would run on JDK 1.6. I have never noticed any, though I haven't done any formal tests. I sincerely

Tomcat 7 on JDK 6 or JDK 7

Hello, I am running tomcat 7.0.65. Currently the tomcat is running on JDK 1.6. Can someone please confirm if there is any performance impact if tomcat 7 would run on JDK 1.6. Thank you Gokul

Re: [OT] Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

ContainerBase is a HashMap and the >>> entries are not ordered. >>> >>> Note that >>> 1) modern JRE uses random seed when evaluating String hash code to >>> mitigate hash collision attacks, so the order will be different on >>> different runs >

Re: Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

o the order will be different on >> different runs > > [citation needed] > > Oracle's Java 8 does not do this, nor do I suspect any other JREs out > there, otherwise Serialization of things like HashMap would break all > over the place. > > One could argue that mo

Re: Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

Konstantin, On 12/31/15 12:56 PM, Konstantin Kolinko wrote: > 2015-12-31 12:41 GMT+03:00 Tomasz Macnar : >> Thanks for answer. >> I understand that application deploy order is the key to get context to >> deployed applicaitons (when application isn't deployed i can't get

Re: Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

On 31/12/2015 07:40, Tomasz Macnar wrote: > Hi, > > I have problem with get ROOT servlet context from other application (on > the same server) in tomcat 8.0.30. > My code look this: > > public class TestServlet extends HttpServlet { > > @Override > public void init() throws

Re: Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

Thanks for answer. I understand that application deploy order is the key to get context to deployed applicaitons (when application isn't deployed i can't get it context - it is clear). But ROOT application is deployed before app1, but i can't get ROOT context from app1. *Is it in tomcat 8

Re: Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

2015-12-31 12:41 GMT+03:00 Tomasz Macnar : > Thanks for answer. > I understand that application deploy order is the key to get context to > deployed applicaitons (when application isn't deployed i can't get it > context - it is clear). > But ROOT application is deployed

Problem with get ROOT context in servlet on tomcat 8.0.30 (jdk 1.7.0_79)

Hi, I have problem with get ROOT servlet context from other application (on the same server) in tomcat 8.0.30. My code look this: public class TestServlet extends HttpServlet { @Override public void init() throws ServletException { ServletContext servletContext =

Re: How to build tc-natvie for solaris sparc 64 bit using 64 bit java JDK

the* /usr/jdk/jdk1.7.0_80/bin/java -version java version "1.7.0_80"Java(TM) SE Runtime Environment (build 1.7.0_80-b15)Java HotSpot(TM) Server VM (build 24.80-b11, mixed mode) *export JAVA_HOME=/usr/jdk/jdk1.7.0_80* *./configure --with-apr=/usr/local/apr/bin/apr-1-config --with-java-home=

Re: How to build tc-natvie for solaris sparc 64 bit using 64 bit java JDK

HI Rainer, Interestingly i tried this as well. *APR,* *CC="cc" CFLAGS="-m64" LDFLAGS="-m64" ./configure* *TC-native,* *CC="cc" CFLAGS="-m64 -fPIC" LDFLAGS="-m64" ./configure --with-apr=/usr/local/apr/bin/apr-1-config --with-java-h

Re: How to build tc-natvie for solaris sparc 64 bit using 64 bit java JDK

HI Rainer, Thanks i was able to succeed this step but still tomcat is not starting. *APR,* CFLAGS="-m64" ./configure *TC-native,* * CFLAGS="-m64" ./configure --with-apr=/usr/local/apr/bin/apr-1-config --with-java-home=/usr/jdk/instances/jdk1.7.0/ --with-ssl=/usr/local/s

Re: How to build tc-natvie for solaris sparc 64 bit using 64 bit java JDK

Am 12.12.2015 um 18:29 schrieb Nithesh Kb: HI Rainer, Interestingly i tried this as well. *APR,* *CC="cc" CFLAGS="-m64" LDFLAGS="-m64" ./configure* *TC-native,* *CC="cc" CFLAGS="-m64 -fPIC" LDFLAGS="-m64" ./configure --with-a

Re: How to build tc-natvie for solaris sparc 64 bit using 64 bit java JDK

"-m64 -fPIC" LDFLAGS="-m64" ./configure >> --with-apr=/usr/local/apr/bin/apr-1-config >> --with-java-home=/usr/jdk/jdk1.7.0_80/ --with-ssl=/usr/local/ssl >> --prefix=/tomcat* >> >> *But i get this error,* >> >> *ld: fatal: file /usr

Re: How to build tc-native for solaris sparc 64 bit using 64 bit java JDK

olaris-jdk.html > > *when i check the* > > /usr/jdk/jdk1.7.0_80/bin/java -version > java version "1.7.0_80"Java(TM) SE Runtime Environment (build > 1.7.0_80-b15)Java HotSpot(TM) Server VM (build 24.80-b11, mixed mode) > > *export JAVA_HOME=/usr/jdk/jdk1.7.0_80* >

Re: How to build tc-native for solaris sparc 64 bit using 64 bit java JDK

HI Chris, Thanks for your reply. Solaris 64bit JDK requires 32 bit JDK *http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html#install-svr4 <http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html#install-svr4>* "*Install

How to build tc-natvie for solaris sparc 64 bit using 64 bit java JDK

*HI, I'm using Solaris sparc 64 bit machine. i wanted to build tc native using 64 bit version of java.* *i installed java in my Solaris box by referring* http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html *when i check the* /usr/jdk/jdk1.7.0_80/bin/java -version java

Re: How to Upgrade Java JDK 7 to JDK8 with Keystore SSL Certificate in Tomcat 7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ignacio, On 9/10/15 6:01 PM, Ignacio Barragan wrote: > I have Tomcat 7.0.42 on a Windows 2008R2 server. I’m pretty new to > Tomcat. > > It uses Java JDK and is configured with a standard JSSE SSL > certificate. How do

How to Upgrade Java JDK 7 to JDK8 with Keystore SSL Certificate in Tomcat 7

I have Tomcat 7.0.42 on a Windows 2008R2 server. I’m pretty new to Tomcat. It uses Java JDK and is configured with a standard JSSE SSL certificate. How do I upgrade Java on an existing Tomcat server? All the documentation is for configuring new installations. I can repeat the whole

AMD 64 version 1.6.0.45 jdk needed

Hello I have a strange architecural problem , I am running the following versions: Processor and arch version [root@evl3301581 java]# file /sbin/init /sbin/init: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), stripped

Re: AMD 64 version 1.6.0.45 jdk needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Joseph, On 2/28/14, 9:55 AM, Joseph Kelly wrote: I have a strange architecural problem , I am running the following versions: Processor and arch version [root@evl3301581 java]# file /sbin/init /sbin/init: ELF 64-bit LSB executable, AMD

Tomcat Maven plugin with JDK 1.7.0_51 and fork set to true

Folks, I'm trying to create some integration tests with the Maven plugin. OS: Fedora 20 64 bit Windows 7 Home Premium 64 bit JRE:1.7.0_51 JDK:1.7.0_51 Maven: 3.12 on Fedora 3.10 on Windows Plugin: 2.2 First thing is I guess I've misunderstood the forktrue/fork

Re: Restrict the use of JDK classes Tomcat 7 or 6

, Charles R chuck.caldar...@unisys.com From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: Restrict the use of JDK classes Tomcat 7 or 6 When you say Java classes, are you talking about re-defining something like java.lang.String? If so, then the servlet spec (3.0

Re: Restrict the use of JDK classes Tomcat 7 or 6

: Restrict the use of JDK classes Tomcat 7 or 6 When you say Java classes, are you talking about re-defining something like java.lang.String? If so, then the servlet spec (3.0: 10.7.2) prohibits web applications from loading classes from any of these packages from a web application

Re: Restrict the use of JDK classes Tomcat 7 or 6

a Permission class? Thank you very much. 2013/10/23 Caldarale, Charles R chuck.caldar...@unisys.com From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: Restrict the use of JDK classes Tomcat 7 or 6 When you say Java classes, are you talking about re-defining

  1   2   3   4   5   >