Re: Tomcat not syncing existing sessions on restart

2024-02-08 Thread Manak Bisht
On Fri, Feb 9, 2024 at 3:25 AM Mark Thomas wrote: > Same JRE? > Yes, 8.0.402 Generally, I wouldn't use 0.0.0.0, I'd use a specific IP address. I'm > not sure how the clustering would behave with 0.0.0.0 > That's the problem really. Using the DNS name or IP address causes the following error -

Tomcat Instance unable to connect to DB with TCPS

2024-02-08 Thread Kebret, Michael
Tomcat version 9.0.83 running on Linux redhat 7 java 11.0.20. When changing the protocol from TCP to TCPS in Catalina.properties and in server.xml we have attribute truststorePassword= (tested with both cleartext and encrypted) password connection is refused to the DB and get the below

Re: Getting provider/properties from jaspic-providers.xml to my ServerAuthModule

2024-02-08 Thread Mark Thomas
On 08/02/2024 14:37, Ryan Esch wrote: I'm using Tomcat 9. I have a provider in jaspic-providers.xml: I am not sure how to get these properties to my ServerAuthModule. I have a ServletContextListener and can see that the jaspic-providers.xml file is being processed if I call:

Re: Persistent Manager Implementation Question

2024-02-08 Thread Mark Thomas
Try turning on ALL logging for the org.apache.catalina.session package. Mark On 08/02/2024 20:49, Miguel Vidal wrote: demo4.zip Hello, Specifications Windows 10 Tomcat 8.5 this is a configuration

Re: [EXT]Re: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Mark Thomas
Confirmed this is user error. There is no bug in the migration tool. Steps to demonstrate this: - Create new, blank Eclipse dynamic web project - Add provided servlet code - Add required libraries - Remove referenced to internal logging code - Add web.xml with basic mapping to "/test" - Export

Re: Tomcat not syncing existing sessions on restart

2024-02-08 Thread Mark Thomas
On 07/02/2024 11:43, Manak Bisht wrote: I think I have narrowed down the problem. For Tomcat 9 (v9.0.85), using 0.0.0.0 for the local member and receiver works fine. However, the same does not work in Tomcat 8.5 (v8.5.98). Same JRE? Generally, I wouldn't use 0.0.0.0, I'd use a specific IP

Persistent Manager Implementation Question

2024-02-08 Thread Miguel Vidal
demo4.zip Hello, Specifications Windows 10 Tomcat 8.5 this is a configuration question . the tomcat specification that works : https://tomcat.apache.org/tomcat-8.0-doc/config/manager.html Im trying to

RE: [EXT]Re: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Rick Noel
No I cannot compile from command line. But I do not really care how eclipse compiles my class anyway. All I know is that eclipse compiles the class without errors. Using the jars I tell it to. (all the jars run through the migration tool) But Tomcat 10 can not compile the class using those same

Re: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Rob Sargent
> On Feb 8, 2024, at 9:04 AM, Rick Noel wrote: > > I built my app in Eclipse and the build path is set to use the migrated > jar. > It compiles without error on Eclipse and using the migrated jar. I have that > same migrated jar in the Tomcat lib > But when tomcat 10 compiles it does

RE: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Rick Noel
I built my app in Eclipse and the build path is set to use the migrated jar. It compiles without error on Eclipse and using the migrated jar. I have that same migrated jar in the Tomcat lib But when tomcat 10 compiles it does not compile I have also used the migration tool on my .war that

Re: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Mark Thomas
On 08/02/2024 14:38, Rick Noel wrote: My code uses no javax.server code other that what is in the third party jar. Then you need to fix your build system that is compiling your code against the original xmlrpc-server3.1.3.jar rather than the migrated version. Is it not the third part jar

RE: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Rick Noel
My code uses no javax.server code other that what is in the third party jar. Is it not the third part jar that needs to stop using javax.server ? Where in my code does it use javax.server, other than from classes in package org.apache.xmlrpc? package com.radiovoodoo.xmlrpc; import

Getting provider/properties from jaspic-providers.xml to my ServerAuthModule

2024-02-08 Thread Ryan Esch
I'm using Tomcat 9. I have a provider in jaspic-providers.xml:                 I am not sure how to get these properties to my ServerAuthModule. I have a ServletContextListener and can see that the jaspic-providers.xml file is being processed if I call: AuthConfigFactory factory =

Re: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Mark Thomas
On 08/02/2024 14:17, Rick Noel wrote: My class is RVXmlRpcServlet and below is the compile error that happens when I use the xmlrpc-server3.1.3.jar after that jar has been run through the migration tool jakartaee-migration-1.0.7 That same class throws NO compile error on Tomcat 9 using

RE: [EXT]Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Rick Noel
My class is RVXmlRpcServlet and below is the compile error that happens when I use the xmlrpc-server3.1.3.jar after that jar has been run through the migration tool jakartaee-migration-1.0.7 That same class throws NO compile error on Tomcat 9 using xmlrpc-server3.1.3.jar Here is the compile

Re: jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Mark Thomas
On 08/02/2024 13:45, Rick Noel wrote: Our application uses classes in this jar xmlrpc-server3.1.3.jar .(it is the latest version) We are trying to migrate to Tomcat 10 but that jar uses the javax.server. package classes instead of the needed jakarta.server. pacakage. I have tried

jakartaee-migration-1.0.7 migration tool failure

2024-02-08 Thread Rick Noel
Our application uses classes in this jar xmlrpc-server3.1.3.jar .(it is the latest version) We are trying to migrate to Tomcat 10 but that jar uses the javax.server. package classes instead of the needed jakarta.server. pacakage. I have tried running this jar trough the latest Tomcat