Mark,
So if my customer object is failing to get set in the session replication,
I could add this to the config snippet?
sessionAttributeNameFilter="customer"
so like this?...
Is there a way to configure DeltaManager or the Cluster element so it does not
cause my application to throw this error.
22-Mar-2024 10:56:34.382 SEVERE [http-nio-8586-exec-5]
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
servlet [jsp] in context with path
One possible workaround is to precompile the JSP's at build time.
https://tomcat.apache.org/tomcat-9.0-doc/jasper-howto.html#Web_Application_Compilation
-Tim
On Fri, Mar 22, 2024 at 1:37 AM Subodh Joshi
wrote:
>
> Why i am doing this exercise?
> In our some of the deployed linux environment
Thanks Chuck great link to lots of good stuff
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-Original Message-
From: Chuck Caldarale
Sent: Thursday, March 21, 2024 4:00 PM
To: Tomcat Users List
Subject: [EXT]Re: [EXT]Re: Tomcat 10 waning that
On 22/03/2024 15:15, Rick Noel wrote:
Is there a way to configure DeltaManager or the Cluster element so it does not
cause my application to throw this error.
22-Mar-2024 10:56:34.382 SEVERE [http-nio-8586-exec-5]
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
Linux has "auditd" tool to log file system changes:
https://www.redhat.com/sysadmin/configure-linux-auditing-auditd
-Harri
-Original Message-
From: Subodh Joshi
Sent: perjantai 22. maaliskuuta 2024 7.36
To: Tomcat Users List
Subject: Re: Tomcat Internal Architect for JSP compilation?
Robert,
On 3/21/24 15:31, Robert Turner wrote:
We receive the sessionWillPassivate and sessionDidActivate callbacks
on startup. Odd that you are not. That's how we achieve the same.
On 3/21/24 16:21, Robert Turner wrote:
Just to add a bit more information, our handler class, for better or for
All,
On 3/22/24 09:33, Robert Turner wrote:
On Fri, Mar 22, 2024 at 9:28 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
Robert,
On 3/21/24 15:31, Robert Turner wrote:
We receive the sessionWillPassivate and sessionDidActivate callbacks
on startup. Odd that you are not. That's
On Fri, Mar 22, 2024 at 9:28 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Robert,
>
> On 3/21/24 15:31, Robert Turner wrote:
> > We receive the sessionWillPassivate and sessionDidActivate callbacks
> > on startup. Odd that you are not. That's how we achieve the same.
> On
Simon,
On 3/21/24 12:39, Simon Niederberger wrote:
Hi Chris
Personally I'd go with
XML_INPUT_FACTORY =
XMLInputFactory.newFactory(XMLInputFactory.class.getName(),
EncodingDetector.class.getClassLoader());
allowing me to place my own JAR in common/lib if I really want to (the
only scenario I
Subodh,
On 3/22/24 01:36, Subodh Joshi wrote:
Hi Chris
Thanks for your response.
So i added below properties in application.properties file
spring.mvc.cache-control.cache-allowed=false
and then Deleted the /tmp/tomcat directory . So now when i restart the
server A.jsp only fail with 500
On 22/03/2024 15:43, Rick Noel wrote:
Mark,
So if my customer object is failing to get set in the session replication,
I could add this to the config snippet?
sessionAttributeNameFilter="customer"
You set that to the attributes you DO want to replicate, not the ones
you don't.
Mark
so
All,
On 3/22/24 09:59, Christopher Schultz wrote:
All,
On 3/22/24 09:33, Robert Turner wrote:
On Fri, Mar 22, 2024 at 9:28 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
Robert,
On 3/21/24 15:31, Robert Turner wrote:
We receive the sessionWillPassivate and
Robert.
On 3/22/24 14:11, Robert Turner wrote:
Thanks for figuring it out -- I will keep that in mind when I go to split
our "mega session object" up as that will impact some of the decisions for
sure.
Yeah, I guess you end up with a "dummy object" on the session as a result
-- I guess we got
I do not want to replicate customer because that class does not implement
serializable
I was looking for someway that the Manager would NOT try to replicate it
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-Original Message-
From: Mark Thomas
Sent: Friday, March
So setting...
sessionAttributeNameFilter="customer"
does not work,
still getting the error java.lang.IllegalArgumentException: setAttribute:
Non-serializable attribute : customer
Do I need to set this also?
sessionAttributeValueClassNameFilter=
Hi guys.
Tomcat 9.0.87 (and Tomcat 9.0.76)
Ubuntu 22.04 (and Red hat 8)
java 8 : openjdk version "1.8.0_382"
protocol: HTTP
I have migrated an application from tomcat 7 (7.0.76) to tomcat 9.0.76 (and
also to tomcat 9.0.87)
After upgrading to Tomcat 9.0.76, the web page is not displaying
Rick,
On 3/22/24 13:33, Rick Noel wrote:
I do not want to replicate customer because that class does not
implement serializable
I was looking for someway that the Manager would NOT try to replicate
it
This is an allow-list which is much more secure than a deny-list.
It's a regular
Thank you very much Chris
The classes my app uses should be serialize anyway so I just go that route.
But thanks for that code snippet too
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-Original Message-
From: Christopher Schultz
Sent: Friday, March 22, 2024 2:36
Very cool Chris, thanks for the quick reaction!
Simon out
On Fri, Mar 22, 2024 at 1:41 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Simon,
>
> On 3/21/24 12:39, Simon Niederberger wrote:
> > Hi Chris
> >
> > Personally I'd go with
> >
> > XML_INPUT_FACTORY =
> >
Thanks for figuring it out -- I will keep that in mind when I go to split
our "mega session object" up as that will impact some of the decisions for
sure.
Yeah, I guess you end up with a "dummy object" on the session as a result
-- I guess we got lucky with ours -- our handlers on the session
21 matches
Mail list logo