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
:29, Mark Thomas wrote:
>>>>> On 27/06/2020 10:19, Thomas Meyer wrote:
>>>>>> Hi,
>>>>>>
>>>>>> A few questions regarding tomcat session replication:
>>>>
>>>>> load-balancing and session replicati
>>>>> Hi,
>>>>>
>>>>> A few questions regarding tomcat session replication:
>>>
>>>> load-balancing and session replication are two separate parts of
>>>> an overall clustering solution.
>>>
>>>>> 1)
Am 30. Juni 2020 11:07:36 MESZ schrieb Mark Thomas :
>On 29/06/2020 21:41, Christopher Schultz wrote:
>> Mark,
>>
>> On 6/27/20 05:29, Mark Thomas wrote:
>>> On 27/06/2020 10:19, Thomas Meyer wrote:
>>>> Hi,
>>>>
>>>> A few ques
On 29/06/2020 21:41, Christopher Schultz wrote:
> Mark,
>
> On 6/27/20 05:29, Mark Thomas wrote:
>> On 27/06/2020 10:19, Thomas Meyer wrote:
>>> Hi,
>>>
>>> A few questions regarding tomcat session replication:
>
>> load-balancing and session
s Meyer wrote:
>>>> Hi,
>>>>
>>>> A few questions regarding tomcat session replication:
>>>
>>> load-balancing and session replication are two separate parts of
>>> an overall clustering solution.
>>>
>>>> 1) is t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thomas,
On 6/27/20 05:52, Thomas Meyer wrote:
> Am 27. Juni 2020 11:29:03 MESZ schrieb Mark Thomas
> :
>> On 27/06/2020 10:19, Thomas Meyer wrote:
>>> Hi,
>>>
>>> A few questions regarding tomcat sessio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 6/27/20 05:29, Mark Thomas wrote:
> On 27/06/2020 10:19, Thomas Meyer wrote:
>> Hi,
>>
>> A few questions regarding tomcat session replication:
>
> load-balancing and session replication are two separate parts
Am 27. Juni 2020 11:29:03 MESZ schrieb Mark Thomas :
>On 27/06/2020 10:19, Thomas Meyer wrote:
>> Hi,
>>
>> A few questions regarding tomcat session replication:
>
>load-balancing and session replication are two separate parts of an
>overall clustering solution.
>
On 27/06/2020 10:19, Thomas Meyer wrote:
> Hi,
>
> A few questions regarding tomcat session replication:
load-balancing and session replication are two separate parts of an
overall clustering solution.
> 1) is the jvmRoute attribute on Engine object necessary for session
> repl
Hi,
A few questions regarding tomcat session replication:
1) is the jvmRoute attribute on Engine object necessary for session replication
to work correctly?
2) does session replication only work correctly with sticky load balancer
routing?
My setup is
1) load balancer without sticky session
On 29 September 2017 15:38:12 BST, "Singh, Rahul (CWM-NR)"
wrote:
>Hi,
>We are using Tomcat 7
>My question is - Why does Tomcat Session Replication require Sticky
>sessions to be enabled?
It doesn't.
>We cannot have a sticky session setup in our servers, due
Hi,
We are using Tomcat 7
My question is - Why does Tomcat Session Replication require Sticky sessions to
be enabled?
We cannot have a sticky session setup in our servers, due to policy issues. To
maintain session state across different machines, we were planning to use
session replication. But
Good Day!
In the documentation, it says that with autobind, if port is unavailable it
will try to work its way up to the port+autobind.
But Members' port and Receiver's port should be the same. Is this correct?
I would like to ask how does port behaves on Receiver with autobind and the
Members
Hi,
I'm using tomcat clustering of 2 tomcats, and session replication via
backup manager.
on session creation in one tomcat instance, the other tomcat replicates the
session successfully but the attribute list is empty no matter how much i
add to it. (the primary session attribute list is fine)
a
To answer my own questions:
On 04/09/2013 14:18, Willem Fibbe wrote:
> ...
> Now I was wondering 2 things:
> - if a Tomcat node restarts, will it be possible that it is trying to receive
> sessions from itself, rather than one or more of the other nodes? Or: should
> I configure a different serv
Hi,
As multicast seems to be giving problems sometimes in our network, we're trying
to also setup static
membership. Note that we want the multicast membership service to be still
functioning.
To do this, I configured the following in server.xml (simplified for brevity)
on all nodes the same,
point is valid, after the user leaves secure.site.com he
> will probably never come back and there is no need to keep his
> session (noone pays twice ;-)).
You obviously need to change your business model. :)
> But I assume tomcat session replication support doesn't support
>
I don't get the relation, 10x100 =
1000, not 10.000 ;-)
But the point is valid, after the user leaves secure.site.com he will
probably never come back and there is no need to keep his session
(noone pays twice ;-)).
But I assume tomcat session replication support doesn't support
sessi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leon,
On 11/16/11 5:06 PM, Leon Rosenberg wrote:
> User logins on http://www.site.fr, a new session is created. User
> uses the site, attributes are written and read... User clicks a
> special link and is redirected to https://secure.site.com -
> secu
Hello,
I'm researching possible solutions for a following scenario and am not
sure whether tomcat session replication can support it:
My site is normally available under www.site.com, www.site.fr,
www.site.de etc, for 22 different countries and a total of 500 domains
(partners). Usually a
> filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.html;.*\.css;.*\.txt;"/>
>className="org.apache.catalina.ha.session.JvmRouteBinderValve"
> enabled="true" sessionIdAttribute="takeoverSessionid"/>
>
>className="org
) :
What is the problem?? Any pointers, tips or outright solution would be
appreciated!!
--
View this message in context:
http://old.nabble.com/Problem-with-tomcat-session-replication
);
if(ses.getAttribute("monitor_loggedin")!=null){
//loggedin
}
===
I suspect that getThreadLocalRequest().getSession() is not compatible with
the Tomcat Session Replication.
Is there a way to get this working or is
k if someone is logged in:
===
HttpSession ses=this.getThreadLocalRequest().getSession(false);
if(ses.getAttribute("monitor_loggedin")!=null){
//loggedin
}
===
I suspect that getThreadLocalRequest().getSession() is not compatible with
the Tomcat Session Replication.
Is there a way to get this
I forgot to state that I am running tomcat 5.5
--
View this message in context:
http://www.nabble.com/Tomcat-Session-Replication-problem-tp16185824p16185828.html
Sent from the Tomcat - User mailing list archive at Nabble.com
===
===
--
View this message in context:
http://www.nabble.com/Tomcat-Session-Replication-problem
Hi!
O Mar, 11-03-2008 ás 22:32 -0600, Filip Hanik - Dev Lists escribiu:
> for it to work you would need to have channelSendOptions="6",
No, it doesn't work too. I've already tried with it... With synchronous
session replication server response is a bit slower (but too much...)
but I have the sam
for it to work you would need to have channelSendOptions="6", however,
not using sticky sessions is a bad strategy, no matter how you look at it.
using sticky sessions, one can take advantage of asynchronous messaging
and hence not affect the overall response time
and other benefits of course
Hi!
I've a session replication problem I don't know how to solve.
I've installed a tomcat cluster with 2 tomcat workers (v6.0.14) and an
apache server 2.2.3 as load balancer, with mod_jk.
I've configured DeltaManager for session replication. When I use sticky
sessions, all works propertly, when
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.
ager app itself.
Regards, Hans.
-Ursprüngliche Nachricht-
Von: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 28. August 2007 19:15
An: Tomcat Users List
Betreff: Re: Tomcat Session Replication at undeploy/install (6.0.14 /
windows)
[EMAIL PROTECTED] wrote:
&g
[EMAIL PROTECTED] wrote:
Hello,
if I reload a context, all sessions are going to be
serialized and deserialized automatically.
Is the same possible at undeploy / deploy?
yes, works the same way
The problem is, that all users are thrown out of their apps
if we "redeploy" under production.
Hello,
if I reload a context, all sessions are going to be
serialized and deserialized automatically.
Is the same possible at undeploy / deploy?
The problem is, that all users are thrown out of their apps
if we "redeploy" under production.
(I know thats not recommended, but sometimes its really
Hello,
we have a problem replicating sessions using Tomcat.
We are using two servers which are load-balanced using Apache. We want to
achieve session preservation over multiple requests of the same user (he might
be forwarded to different servers for those requests).
What we tried to set up unti
could well be.
depends on your setup...
>
> WARNING: Unable to asynchronously send session with
> id=[88798A041EC3F104045E5C22B47ADE77.jvm1-1151322148155] - message will
> be ignored. java.net.Connect
On Mon, 26 Jun 2006 11:46:43 +0100
Pid <[EMAIL PROTECTED]> wrote:
>
>
> Sean O'Reilly wrote:
>
> > Still having some problems with load balancing and state replication
> > neither of which appear to be working. If i shutdown tomcat on the
> > main server i can still get to the application direc
Sean O'Reilly wrote:
> Still having some problems with load balancing and state replication
> neither of which appear to be working. If i shutdown tomcat on the
> main server i can still get to the application directory from one of
> the other servers but get a 503 error if i try to run any of
(I've manually configured the tcpListenAddress to be the node's main IP.
Obviously it's not 000.000.000.00.)
I've specified JvmRouteBinderValve, JvmRouteSessionIDBinderListener and
ClusterSessionListener.
Sean O'Reilly wrote:
> On Fri, 23 Jun 200
On Fri, 23 Jun 2006 16:43:16 +0100
Pid <[EMAIL PROTECTED]> wrote:
>
>
> Sean O'Reilly wrote:
> > On Fri, 23 Jun 2006 09:05:18 -0500
> > Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> > I am sure it would be easier to use mod_proxy_balancer and
> > mod_proxy_ajp but can't find any documenta
Sean O'Reilly wrote:
> On Fri, 23 Jun 2006 09:05:18 -0500
> Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> I am sure it would be easier to use mod_proxy_balancer and
> mod_proxy_ajp but can't find any documentation anywhere.
My servers didn't have their clocks synchronised, check that.
Als
How are you defining the cluster in your server.xml?
I did this recently, and had a bunch of small problems.
E.g. my server clocks weren't sync'd.
I found that enabling just the SimpleTcpCluster element (without all the
rest) helped me get up and running.
Sean O'Reilly wrote:
> On Fri, 23 Jun 2
Sean O'Reilly wrote:
On Fri, 23 Jun 2006 10:00:36 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Sean O'Reilly wrote:
On Fri, 23 Jun 2006 09:05:18 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Hi Guys,
I appear to be finally getting somewhere with the
On Fri, 23 Jun 2006 10:00:36 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> Sean O'Reilly wrote:
> > On Fri, 23 Jun 2006 09:05:18 -0500
> > Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> >
> >
> >>> Hi Guys,
> >>>
> >>> I appear to be finally getting somewhere with the in-memo
Sean O'Reilly wrote:
On Fri, 23 Jun 2006 09:05:18 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Hi Guys,
I appear to be finally getting somewhere with the in-memory state
replication but am now getting the following error when starting up
my tomcat instances/
WARNING: Manager [/
On Fri, 23 Jun 2006 09:05:18 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
>
> > Hi Guys,
> >
> > I appear to be finally getting somewhere with the in-memory state
> > replication but am now getting the following error when starting up
> > my tomcat instances/
> >
> > WARNING: Manager
Hi Guys,
I appear to be finally getting somewhere with the in-memory state
replication but am now getting the following error when starting up my
tomcat instances/
WARNING: Manager [/jsp-examples], requesting session state from
org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.4.121:
On Thu, 22 Jun 2006 15:39:09 +0100
Pid <[EMAIL PROTECTED]> wrote:
> In each case it's the ROOT context, so is it appending "" where
> there's no Context name/path: ie
>
> SEVERE: Context manager doesn't exist:host1+context1
>
> where context1=""
> ?
>
> It would still seem that the name parame
In each case it's the ROOT context, so is it appending "" where there's
no Context name/path: ie
SEVERE: Context manager doesn't exist:host1+context1
where context1=""
?
It would still seem that the name parameter supplied to the
getManagerName is carrying over it's previous value, and appendin
Makes sense, can we please ask you to open up a bug for us,
http://issues.apache.org/bugzilla/
thanks
Filip
Pid wrote:
OK,
I'm probably being dense here.
(There's only 1 context in each host, the ROOT context)
If I take the Host/Context offline in one node and restart it, the logs
on that no
OK,
I'm probably being dense here.
(There's only 1 context in each host, the ROOT context)
If I take the Host/Context offline in one node and restart it, the logs
on that node start showing the following:
SEVERE: Context manager doesn't exist:host1
As the Context doesn't exist, which is the sa
Hmm,
look at o.a.c.cluster.tcp.SimpleTcpCluster
L 626ff
private String getManagerName(String name, Manager manager) {
String clusterName = name ;
if(getContainer() instanceof Engine) {
Container context = manager.getContainer() ;
if(context != null &&
Filip Hanik - Dev Lists wrote:
> if the cluster is put in the engine element, the context names are
> prefixed with the engine name, since you can have multiple contexts with
> the same name in different host
> when reloading a context, you'll get these errors cause the context is
> not available
if the cluster is put in the engine element, the context names are
prefixed with the engine name, since you can have multiple contexts with
the same name in different host
when reloading a context, you'll get these errors cause the context is
not available during the reload
this will be fixed w
I'm seeing an issue on 5.5.17 with a 2 node cluster config.
When a context is reloaded, it sends the context node name incorrectly
to the cluster.
E.g. context is called "website1"
SEVERE: Context manager doesn't exist:website1website1
The config I'm using is exactly the same as the default from
62 matches
Mail list logo
