PM
To: Tomcat Users List ; Rick Noel
Subject: Re: [EXT]Re: Tomcat session replication issue -
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute :
Rick,
On 3/22/24 13:33, Rick Noel wrote:
> I do not want to replicate customer because that class does not
> imp
om
-Original Message-
From: Mark Thomas
Sent: Friday, March 22, 2024 11:32 AM
To: users@tomcat.apache.org
Subject: [EXT]Re: Tomcat session replication issue -
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute :
On 22/03/2024 15:15, Rick Noel wrote:
Is ther
22, 2024 1:27 PM
To: users@tomcat.apache.org
Subject: Re: [EXT]Re: Tomcat session replication issue -
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute :
On 22/03/2024 15:43, Rick Noel wrote:
> Mark,
>
> So if my customer object is failing to get set in th
Westwood One
rn...@westwoodone.com
-Original Message-
From: Mark Thomas
Sent: Friday, March 22, 2024 11:32 AM
To: users@tomcat.apache.org
Subject: [EXT]Re: Tomcat session replication issue -
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute :
On 22/03/2024 15:15,
the application code itself)
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-Original Message-
From: Rick Noel
Sent: Friday, March 22, 2024 11:43 AM
To: Tomcat Users List
Subject: RE: [EXT]Re: Tomcat session replication issue -
java.lang.IllegalArgumentExceptio
t: [EXT]Re: Tomcat session replication issue -
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute :
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.
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
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 [##00
After playing with static clustering a few more days, I still ran
headlong into a wall with this.
I decided to go back to multicast, and try BackupManager instead of
DeltaManager, and it now seems to be restarting correctly, as long as my
timeout was high enough for the 15+ second AbstractMapR
Thank you David, but this is happening on service restart, not operating
system restart. But, yes, you can modify startup scripts to happen in
sequence, or add a sleep delay.
Thank you,
-Anthony
On 3/25/2016 10:11 AM, David kerber wrote:
On 3/25/2016 9:41 AM, Anthony Sturchio wrote:
Hello
Thanks for the response. I apologize if I'm using the incorrect
terminology here, as this is one of the smaller "hats" that I wear at work.
Basically, coldfusion runs on top of a (possibly customized) tomcat
backend. Each instance has its own server.xml and web.xml. As best I
can figure, w
On 3/25/2016 9:41 AM, Anthony Sturchio wrote:
Hello
We recently updated our Coldfusion 10 server to update 18, which moved
us up to Tomcat 7.0.64, and we are now experiencing issues when
restarting a CF instance. I understand that this is not a coldfuison
forum, but since CF10 is based on top o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anthony,
On 3/25/16 9:41 AM, Anthony Sturchio wrote:
> We recently updated our Coldfusion 10 server to update 18, which
> moved us up to Tomcat 7.0.64, and we are now experiencing issues
> when restarting a CF instance. I understand that this is not
Hello
We recently updated our Coldfusion 10 server to update 18, which moved
us up to Tomcat 7.0.64, and we are now experiencing issues when
restarting a CF instance. I understand that this is not a coldfuison
forum, but since CF10 is based on top of a tomcat back end, which is
where the iss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dhaval,
On 12/9/13, 3:04 PM, Dhaval Jaiswal wrote:
> setting of session replication worked well. However, we do have
> threading in some products. Like we are hitting the target API and
> getting response from there servers. If will not get the resp
setting of session replication worked well. However, we do have threading
in some products. Like we are hitting the target API and getting response
from there servers. If will not get the response will hit them after some
time and in this case threading not handled by session replication because
of
Hi all,
I am using Tomcat 5.5 as both Web Server and Web Container.
I have 4 tomcat instances A,B,C,D - 2 each on 2 Web Server boxes.
There's a
hardware load balancer sitting before these that routes to each of the
4
IP/ports.
I haven't used method described in the TOmcat 5.5 docs on the
tomcat.
17 matches
Mail list logo
