November 2017 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-629) Upgrade jboss-parent to 25

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-629?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-629: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade jboss-parent to 25 > -------------------------- > > Key: MODCLUSTER-629 > URL: https://issues.jboss.org/browse/MODCLUSTER-629 > Project: mod_cluster > Issue Type: Component Upgrade > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: jdk9 > Fix For: 2.0.0.Alpha1 > > > Changelog: https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-25, mostly JDK9 upgrades -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-469) Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-469?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-469: -------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/303 (was: https://github.com/modcluster/mod_cluster/pull/160) > Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory > --------------------------------------------------------------------------------------------------------- > > 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, 1.4.0.Alpha1 > Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone > Reporter: Eric Vernier > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.4.0.Alpha2, 2.0.0.Alpha1 > > > 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 (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-469) Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-469?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-469: -------------------------------------- Priority: Critical (was: Major) > Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory > --------------------------------------------------------------------------------------------------------- > > 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, 1.4.0.Alpha1 > Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone > Reporter: Eric Vernier > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.4.0.Alpha2, 2.0.0.Alpha1 > > > 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 (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-469) Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-469?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-469: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory > --------------------------------------------------------------------------------------------------------- > > 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, 1.4.0.Alpha1 > Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone > Reporter: Eric Vernier > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha2, 2.0.0.Alpha1 > > > 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 (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-469) Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-469?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-469: -------------------------------------- Summary: Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory (was: Tomcat8 standalone : jvmRoute not added to jessionid cookie when generated as UUID by JvmRouteFactory) > Tomcat 8 container integration does not add jvm-route to JSESSIONID when generated by UUIDJvmRouteFactory > --------------------------------------------------------------------------------------------------------- > > 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, 1.4.0.Alpha1 > Environment: Apache 2.4, ModCluster 1.3.1, Tomcat 8.0 standalone > Reporter: Eric Vernier > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha2, 2.0.0.Alpha1 > > > 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 (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-629) Upgrade jboss-parent to 25

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-629?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-629: -------------------------------------- Labels: jdk9 (was: ) > Upgrade jboss-parent to 25 > -------------------------- > > Key: MODCLUSTER-629 > URL: https://issues.jboss.org/browse/MODCLUSTER-629 > Project: mod_cluster > Issue Type: Component Upgrade > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: jdk9 > Fix For: 2.0.0.Alpha1 > > > Changelog: https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-25, mostly JDK9 upgrades -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-629) Upgrade jboss-parent to 25

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-629?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-629: -------------------------------------- Description: Changelog: https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-25, mostly JDK9 upgrades (was: Changelog: https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-25) > Upgrade jboss-parent to 25 > -------------------------- > > Key: MODCLUSTER-629 > URL: https://issues.jboss.org/browse/MODCLUSTER-629 > Project: mod_cluster > Issue Type: Component Upgrade > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: jdk9 > Fix For: 2.0.0.Alpha1 > > > Changelog: https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-25, mostly JDK9 upgrades -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-629) Upgrade jboss-parent to 25

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-629?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-629: -------------------------------------- Description: Changelog: https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-25 > Upgrade jboss-parent to 25 > -------------------------- > > Key: MODCLUSTER-629 > URL: https://issues.jboss.org/browse/MODCLUSTER-629 > Project: mod_cluster > Issue Type: Component Upgrade > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > Changelog: https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-25 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-629) Upgrade jboss-parent to 25

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-629?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-629: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/302 > Upgrade jboss-parent to 25 > -------------------------- > > Key: MODCLUSTER-629 > URL: https://issues.jboss.org/browse/MODCLUSTER-629 > Project: mod_cluster > Issue Type: Component Upgrade > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-628) Travis CI: Add oraclejdk9 to the matrix

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-628?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-628: -------------------------------------- Priority: Critical (was: Major) > Travis CI: Add oraclejdk9 to the matrix > --------------------------------------- > > Key: MODCLUSTER-628 > URL: https://issues.jboss.org/browse/MODCLUSTER-628 > Project: mod_cluster > Issue Type: Task > Components: CI & Packaging > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Labels: jdk9 > Fix For: 1.4.0.Alpha2, 2.0.0.Alpha1, 1.3.9.Final > > > The oraclejdk9 is now available on Travis CI so all branches since 1.3 should test it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues November 2017