eated correctly on different
node (always happened for Flex channels and sometimes for Ajax requests).
Thanks,
Andrey.
--
View this message in context:
http://old.nabble.com/Always-load-balance-to-same-box-with-different-tomcat-contexts-tp27946266p27984292.html
Sent from the Tomcat - User mailing
Guys,
On Fri, Mar 19, 2010 at 5:12 PM, Mark Thomas wrote:
> On 19/03/2010 12:16, 2smart4u wrote:
>
> As per the thread title the OP wanted to:
> "Always load balance to same box with different tomcat contexts"
>
I understood it that way that he always wanted to loadbal
SSO Valve:
>
> So to my understanding it *is* about clustering and different hosts -
> or am I wrong here?
As per the thread title the OP wanted to:
"Always load balance to same box with different tomcat contexts"
Clustering appears to be giving them some difficulties as they said:
Mark,
had a bad day?
On Fri, Mar 19, 2010 at 12:46 PM, Mark Thomas wrote:
> The question was how to make session stickiness apply to all applications on
> a host. Clustering was mentioned but isn't relevant to this question (and
> the OP's original post seemed to suggest they were having issues
On 19/03/2010 12:38, 2smart4u wrote:
I think you might be missing something here.
If I got the OP correct, it's not only about loadbalancing but also
about maintaing the session between different Tomcat instances.
The question was how to make session stickiness apply to all
applications on a ho
On Fri, Mar 19, 2010 at 11:54 AM, Mark Thomas wrote:
>
>> 2) There is cookie in browser - it will loadbalance to engine which
>> already
>> has session - since cookie has no context path
>
> Correct.
>
Mark, I think you might be missing something here.
If I got the OP correct, it's not only abou
On 19/03/2010 11:05, Andrey Ilyin wrote:
Does this mean that session/servletContext is shared between contexts?
No.
E.g.
if I have some attribute in session/application contexts in webapp1 would it
be accesible in webapp2?
No. Each webapp will have its own session object although they will all
On Fri, Mar 19, 2010 at 11:05 AM, Andrey Ilyin wrote:
>
>
> Does this mean that session/servletContext is shared between contexts? E.g.
> if I have some attribute in session/application contexts in webapp1 would it
> be accesible in webapp2?
>
when the context is dropped from a Cookie-path, the c
s message in context:
http://old.nabble.com/Always-load-balance-to-same-box-with-different-tomcat-contexts-tp27946266p27950926.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: us
>From the docs:
= [cut] =
If set to true, all paths for session cookies will be set to /. This
can be useful for portlet specification implementations. If not
specified, this attribute is set to false.
= [cut] =
More or less, it drops the context from the Cookie-path, meaning the
cookie is vali
derstand and I need to know if there any risks/downsides of enabling
> this flag.
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://ol
On 18/03/2010 15:22, Andrey Ilyin wrote:
Is there a way to force apache to always rebalance to same box for different
tomcat contexts?
You can try setting emptySessionPath="true" on the connector.
Mark
-
To unsubscribe, e-m
ad-balance-to-same-box-with-different-tomcat-contexts-tp27946266p27946266.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional comman
13 matches
Mail list logo
