On 13/07/2010 21:58, Okubo, Yasushi (TSD) wrote:
>
>
> -Original Message-
> From: Pid [mailto:p...@pidster.com]
> Sent: Friday, June 25, 2010 4:29 AM
> To: Tomcat Users List
> Subject: Re: question for sso session replication in tomcat 6.0.26
>
> On 24/06
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Friday, June 25, 2010 4:29 AM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
On 24/06/2010 21:49, Okubo, Yasushi (TSD) wrote:
> My bad.
>
> I added *.jsp to the filter
Hi Pid
I think I found a problem. Could you tell me how to fix this? Should I
report it to bugzilla?
SingleSignOn sessionEvent is destroying session, but DeltaSession is
notifying session expiration to other node on same cluster.
== singlesignon ==
protected void deregister(String ssoId) {
On 28/06/2010 23:19, Okubo, Yasushi (TSD) wrote:
> On 28/06/2010 21:21, Okubo, Yasushi (TSD) wrote:
>> Yes, I do.
>>
>> >name="webclust2"
>>expireSessionsOnShutdown="false"
>
> Hmm.
>
> Can you unset the DeltaManager name attribute on all of your
in
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Monday, June 28, 2010 4:01 PM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
On 28/06/2010 23:19, Okubo, Yasushi (TSD) wrote:
> On 28/06/2010 21:21, Okubo, Yasushi (TSD) wrote:
>
p
> FINE: Sending application stop events
>
> == singlesignonmessage.java
> public class SingleSignOnMessage implements ClusterMessage, Serializable
> {
>
> public static final int ADD_SESSION = 1;
> public static final int DEREGISTER_SESSION = 2;
> public static final int LO
nday, June 28, 2010 1:09 PM
> To: Tomcat Users List
> Subject: Re: question for sso session replication in tomcat 6.0.26
>
> On 28/06/2010 19:58, Okubo, Yasushi (TSD) wrote:
>>
>> Hi Pid
>>
>> I got more detailed log and it looks like cluster
--Original Message-
> From: Pid [mailto:p...@pidster.com]
> Sent: Monday, June 28, 2010 1:09 PM
> To: Tomcat Users List
> Subject: Re: question for sso session replication in tomcat 6.0.26
>
> On 28/06/2010 19:58, Okubo, Yasushi (TSD) wrote:
>>
>> Hi Pid
>&
Yes, I do.
mailto:p...@pidster.com]
Sent: Monday, June 28, 2010 1:09 PM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
On 28/06/2010 19:58, Okubo, Yasushi (TSD) wrote:
>
> Hi Pid
>
> I got more detailed log and it looks like clustersin
msg.setAction(SingleSignOnMessage.LOGOUT_SESSION);
>
> cluster.sendClusterDomain(msg);
> if (containerLog.isDebugEnabled())
> containerLog.debug("SingleSignOnMessage Send with action
> "
> + msg.getAc
d);
}
protected void deregisterLocal(String ssoId) {
super.deregister(ssoId);
}
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Friday, June 25, 2010 4:29 AM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
On 24
;prop=Home"); %>
>
> -Original Message-
> From: Okubo, Yasushi (TSD)
> Sent: Thursday, June 24, 2010 1:13 PM
> To: 'Tomcat Users List'
> Subject: RE: question for sso session replication in tomcat 6.0.26
>
>
> Hi Pid
>
> I started getting th
onal.com]
> Sent: Tuesday, June 22, 2010 2:17 PM
> To: Tomcat Users List
> Cc: Okubo, Yasushi (TSD)
> Subject: Re: question for sso session replication in tomcat 6.0.26
>
> Are you using a "jvmRoute" setting on your BalancerMember definition
in
> mod_proxy
dyn&prop=Home"); %>
-Original Message-
From: Okubo, Yasushi (TSD)
Sent: Thursday, June 24, 2010 1:13 PM
To: 'Tomcat Users List'
Subject: RE: question for sso session replication in tomcat 6.0.26
Hi Pid
I started getting the following error upon login to one node o
)
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Wednesday, June 23, 2010 1:06 AM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
I'll have to look at the code, but maybe you're being affected by a
recent bug whereby the session
AM
To: 'Tomcat Users List'
Subject: RE: question for sso session replication in tomcat 6.0.26
Thanks Pid
It might be related to the fix for 45255. This is the only one I can see
remotely related. According to this fix, (I might be wrong), but it
looks like once the user is logged-ou
test older Tomcat 6.0.1x today.
Yasushi
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Wednesday, June 23, 2010 1:06 AM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
I'll have to look at the code, but maybe you're bein
sday, June 22, 2010 2:17 PM
> To: Tomcat Users List
> Cc: Okubo, Yasushi (TSD)
> Subject: Re: question for sso session replication in tomcat 6.0.26
>
> Are you using a "jvmRoute" setting on your BalancerMember definition in
> mod_proxy config and on the element in s
pache side or how
the
> virtual host should be set up in httpd.conf to make sso failover work?
>
> Thanks,
> yasushi
>
> -Original Message-
> From: Pid [mailto:p...@pidster.com]
> Sent: Tuesday, June 22, 2010 8:04 AM
> To: Tomcat Users List
> Subject: Re: qu
ost should be set up in httpd.conf to make sso failover work?
>
> Thanks,
> yasushi
>
> -Original Message-
> From: Pid [mailto:p...@pidster.com]
> Sent: Tuesday, June 22, 2010 8:04 AM
> To: Tomcat Users List
> Subject: Re: question for sso session replication in
List
Subject: Re: question for sso session replication in tomcat 6.0.26
On 22/06/2010 15:56, Okubo, Yasushi (TSD) wrote:
> Hi Andrew
>
> In case of no failover, SSO works for all web applications on the same
host. Upon failover [shutting down one node], a user is routed to the
other node,
Ok
I will try to install the latest apache httpd and test again.
Thanks,
yasushi
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Tuesday, June 22, 2010 8:04 AM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
On 22/06/2010 15:56
...@takedasd.com]
Sent: Tuesday, June 22, 2010 7:57 AM
To: Tomcat Users List
Subject: RE: question for sso session replication in tomcat 6.0.26
Hi Andrew
In case of no failover, SSO works for all web applications on the same host.
Upon failover [shutting down one node], a user is routed to the other node
>className="org.apache.catalina.ha.session.JvmRouteBinderValve"
> enabled="true" sessionIdAttribute="takeoverSessionid" />
>
>
>className="org.apache.catalina.ha.session.JvmRouteSessi
: question for sso session replication in tomcat 6.0.26
Oh sorry, I re-read your answer. Not sure why SSO is not working, be
interested to find out though..
AB
On Tue, Jun 22, 2010 at 3:04 PM, Andrew Bruno wrote:
> Hi Yasushi
>
> In your serverl.xml have you added the jvmroute to the Engine
ionidsso] does not have jvmroute info, but only jsessionid
>>> has jvmroute. So, session replication upon failover is working fine, but
>>> singlesionon upon failover is not working on tomcat 6.0.x (including
>>> 6.0.26).
>>>
>>> yasushi
>>>
&g
on replication upon failover is working fine, but
>> singlesionon upon failover is not working on tomcat 6.0.x (including 6.0.26).
>>
>> yasushi
>>
>> -Original Message-
>> From: Andrew Bruno [mailto:andrew.br...@gmail.com]
>> Sent: Monday, June 21,
mail.com]
> Sent: Monday, June 21, 2010 9:18 PM
> To: Tomcat Users List
> Subject: Re: question for sso session replication in tomcat 6.0.26
>
> Looking at the code I think this is wrong
>
> if (!_ssoSessionId.contains("." + jvmRoute)) {
> _ssoSessionId += ".
Looking at the code I think this is wrong
if (!_ssoSessionId.contains("." + jvmRoute)) {
_ssoSessionId += "." + jvmRoute;
response.addCookie(new Cookie(_SSO_SESSION_COOKIE_NAME, _ssoSessionId));
}
The original sessionId will already have the "."+_any_other_jvmRoute
included, so you need to
(including 6.0.26).
yasushi
-Original Message-
From: Andrew Bruno [mailto:andrew.br...@gmail.com]
Sent: Monday, June 21, 2010 9:18 PM
To: Tomcat Users List
Subject: Re: question for sso session replication in tomcat 6.0.26
Looking at the code I think this is wrong
if (!_ssoSessionId.contains
Hi experts
I found this old email from archive in TC 5.5.23.
Does this problem still exist in tomcat 6.0.x or 6.0.26?
When failover occurs, sso session id is updated with new number after
forcing a user to relogin to the application since sso session id is not
replicated and rewritten corr
31 matches
Mail list logo
