mod_cluster-issues October 2015

mod_cluster-issues@lists.jboss.org

1 participants
14 discussions

[JBoss JIRA] (MODCLUSTER-469) Tomcat8 standalone : jvmRoute not added to jessionid cookie when generated as UUID by JvmRouteFactory

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-469?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-469: -------------------------------------- Description: If jvmRoute attribute is not set in server.xml on engine element, ModClusterService generates a jvmRoute (UUID). This UUID is not added in the value of the cookie "jsessionid", so the sticky session doesn't work. When the jvmRoute is defined in the server.xml all works fine. I known no much about lifecyle in Catalina, but my feeling is that ModClusterService generates the jvmRoute (with JvmRouteFactory) after the creation of SessionIdGenerator by the org.apache.catalina.Manager. When ModClusterService injects the generated jvmRoute it's too, the SessionIdGenerator is already created. was: If jvmRoute attribute is not set in server.xml on engine element, ModClusterService generates a jvmRoute (UUID). This UUID is not added in the value of the cookie "jsessionid", so the sticky session doesn't work. When the jvmRoute is defined in the server.xml all works fine. I known no much about lifecyle in Catalina, but my feeling is that ModClusterService generates the jvmRoute (with JvmRouteFactory) after the creation of SessionIdGenerator by the org.apache.catalina.Manager. When ModClusterService injects the generated jvmRoute it's too, the SessionIdGenerator is already created. > Tomcat8 standalone : jvmRoute not added to jessionid cookie when generated as UUID by JvmRouteFactory > ----------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-469 > URL: https://issues.jboss.org/browse/MODCLUSTER-469 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Final > Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone > Reporter: Eric Vernier > Assignee: Radoslav Husar > > If jvmRoute attribute is not set in server.xml on engine element, ModClusterService generates a jvmRoute (UUID). This UUID is not added in the value of the cookie "jsessionid", so the sticky session doesn't work. When the jvmRoute is defined in the server.xml all works fine. > I known no much about lifecyle in Catalina, but my feeling is that ModClusterService generates the jvmRoute (with JvmRouteFactory) > after the creation of SessionIdGenerator by the org.apache.catalina.Manager. When ModClusterService injects the generated jvmRoute it's too, the SessionIdGenerator is already created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-469) Tomcat8 standalone : jvmRoute not added to jessionid cookie when generated as UUID by JvmRouteFactory

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-469?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-469: -------------------------------------- Description: If jvmRoute attribute is not set in server.xml on engine element, ModClusterService generates a jvmRoute (UUID). This UUID is not added in the value of the cookie "jsessionid", so the sticky session doesn't work. When the jvmRoute is defined in the server.xml all works fine. I known no much about lifecyle in Catalina, but my feeling is that ModClusterService generates the jvmRoute (with JvmRouteFactory) after the creation of SessionIdGenerator by the org.apache.catalina.Manager. When ModClusterService injects the generated jvmRoute it's too, the SessionIdGenerator is already created. was: If jvmRoute attribute is not set in server.xml on engine element, ModClusterService generates a jvmRoute (UUID). This UUID is not added in the value of the cookie "jsessionid", so the sticky session doesn't work. When the jvmRoute is defined in the server.xml all works fine. I known no much about lifecyle in Catalina, but my feeling is that ModClusterService generates the jvmRoute (with JvmRouteFactory) after the creation of SessionIdGenerator by the org.apache.catalina.Manager. When ModClusterService injects the generated jvmRoute it's too late, the SessionIdGenerator is already created. > Tomcat8 standalone : jvmRoute not added to jessionid cookie when generated as UUID by JvmRouteFactory > ----------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-469 > URL: https://issues.jboss.org/browse/MODCLUSTER-469 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Final > Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone > Reporter: Eric Vernier > Assignee: Radoslav Husar > > If jvmRoute attribute is not set in server.xml on engine element, ModClusterService generates a jvmRoute (UUID). This UUID is not added in the value of the cookie "jsessionid", so the sticky session doesn't work. When the jvmRoute is defined in the server.xml all works fine. > I known no much about lifecyle in Catalina, but my feeling is that ModClusterService generates the jvmRoute (with JvmRouteFactory) > after the creation of SessionIdGenerator by the org.apache.catalina.Manager. When ModClusterService injects the generated jvmRoute it's too, > the SessionIdGenerator is already created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by yi yin (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] yi yin commented on MODCLUSTER-438: ----------------------------------- can I use both ajp and WebSocket on one apache for loadbalance? e.g. when use http client access to apache,it will redirect to a http webserver. when use WebSocket client access to the same apache,it will redirect to a websocket webserver. > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-432) Multicast discovery does not work on Mac OS X, fails with "Can't assign requested address"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-432?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-432: -------------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: (was: https://github.com/modcluster/mod_cluster/pull/152) Reverted and reopening. > Multicast discovery does not work on Mac OS X, fails with "Can't assign requested address" > ------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-432 > URL: https://issues.jboss.org/browse/MODCLUSTER-432 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Alpha2 > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Priority: Minor > Fix For: 1.3.1.Beta2 > > > Basically that causes 2 tests to fail on macsox (Darwin Kernel Version 13.4.0) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

← Newer
1
2
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2015