February 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-447) ProxyInfo not available in Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-447?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-447: ----------------------------------------- Assignee: Maxime Beck (was: Radoslav Husar) > ProxyInfo not available in Tomcat > --------------------------------- > > Key: MODCLUSTER-447 > URL: https://issues.jboss.org/browse/MODCLUSTER-447 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.10.Final > Environment: mod_cluster 1.2.10, Tomcat 7.0.57 > Reporter: Alexander Schulz > Assignee: Maxime Beck > Fix For: 1.2.10.Final > > > I'm looking for a way to read proxy informations from within an application deployed on a Tomcat 7. > > With the jboss cli I can read the proxies info like this: > /host=xyz/server=abc/subsystem=modcluster:read-proxies-info() > > I looked for the ModClusterListener MBean methods and properties in Tomcat 7. I found this method in ModClusterListener: > /** > * {@inhericDoc} > * > * @see org.jboss.modcluster.ModClusterServiceMBean#getProxyInfo() > */ > @Override > public Map<InetSocketAddress, String> getProxyInfo() { > return this.service.getProxyInfo(); > } > > The problem is that I found no proxyInfo method or attribute at the ModClusterListener MBean. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-447) ProxyInfo not available in Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-447?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-447: ----------------------------------------- Assignee: Radoslav Husar (was: Maxime Beck) > ProxyInfo not available in Tomcat > --------------------------------- > > Key: MODCLUSTER-447 > URL: https://issues.jboss.org/browse/MODCLUSTER-447 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.10.Final > Environment: mod_cluster 1.2.10, Tomcat 7.0.57 > Reporter: Alexander Schulz > Assignee: Radoslav Husar > Fix For: 1.2.10.Final > > > I'm looking for a way to read proxy informations from within an application deployed on a Tomcat 7. > > With the jboss cli I can read the proxies info like this: > /host=xyz/server=abc/subsystem=modcluster:read-proxies-info() > > I looked for the ModClusterListener MBean methods and properties in Tomcat 7. I found this method in ModClusterListener: > /** > * {@inhericDoc} > * > * @see org.jboss.modcluster.ModClusterServiceMBean#getProxyInfo() > */ > @Override > public Map<InetSocketAddress, String> getProxyInfo() { > return this.service.getProxyInfo(); > } > > The problem is that I found no proxyInfo method or attribute at the ModClusterListener MBean. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-447) ProxyInfo not available in Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-447?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-447 at 2/29/16 6:13 PM: -------------------------------------------------------------------- It is the same issue we have in RHQ/JON with mod_cluster. Only a String can work with the tomcat modeler, basically we need to have a method to return a String. was (Author: jfclere): it is the same issue we have in RHQ/JON wityh mod_cluster. Only a String can work with the tomcat modeler, basically we need to have a method to return a String. > ProxyInfo not available in Tomcat > --------------------------------- > > Key: MODCLUSTER-447 > URL: https://issues.jboss.org/browse/MODCLUSTER-447 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.10.Final > Environment: mod_cluster 1.2.10, Tomcat 7.0.57 > Reporter: Alexander Schulz > Assignee: Maxime Beck > Fix For: 1.2.10.Final > > > I'm looking for a way to read proxy informations from within an application deployed on a Tomcat 7. > > With the jboss cli I can read the proxies info like this: > /host=xyz/server=abc/subsystem=modcluster:read-proxies-info() > > I looked for the ModClusterListener MBean methods and properties in Tomcat 7. I found this method in ModClusterListener: > /** > * {@inhericDoc} > * > * @see org.jboss.modcluster.ModClusterServiceMBean#getProxyInfo() > */ > @Override > public Map<InetSocketAddress, String> getProxyInfo() { > return this.service.getProxyInfo(); > } > > The problem is that I found no proxyInfo method or attribute at the ModClusterListener MBean. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-478) session drain wait does not end for JBossWeb 7

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-478?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-478: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/166 Here's a PR that can fix the listener so that it is added and invoked as expected in JBossWeb 7. But after this listener notifies the wait, the wait actually loops back and continues. The session is not removed till some time after the listener is invoked so we can't currently depend upon a listener to wake us up when there are 0 sessions. (see https://issues.jboss.org/browse/WFLY-6294 about that for WildFly) > session drain wait does not end for JBossWeb 7 > ---------------------------------------------- > > Key: MODCLUSTER-478 > URL: https://issues.jboss.org/browse/MODCLUSTER-478 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Environment: -JBoss EAP 6 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > mod_cluster session draining does not properly end when an active session is invalidated. The NotifyOnDestroySessionListener is not invoked because it is not properly added. That listener is added as a ApplicationLifecycleListeners, but JBossWeb 7 invokes ApplicationSessionLifecycleListeners instead upon session expiration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-478) session drain wait does not end for JBossWeb 7

by Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-478: --------------------------------------- Summary: session drain wait does not end for JBossWeb 7 Key: MODCLUSTER-478 URL: https://issues.jboss.org/browse/MODCLUSTER-478 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Environment: -JBoss EAP 6 Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere mod_cluster session draining does not properly end when an active session is invalidated. The NotifyOnDestroySessionListener is not invoked because it is not properly added. That listener is added as a ApplicationLifecycleListeners, but JBossWeb 7 invokes ApplicationSessionLifecycleListeners instead upon session expiration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-454) Versioning of mod_cluster management protocol (MCMP)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-454?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-454: -------------------------------------- Description: * Investigate the current state of MCMP versioning * Design protocol version negotiation * Must be done prior to donation to ASF was: * Investigate the current state of MCMP versioning (probably very limited to none). * Design protocol version negotiation (which part requires the version used?) * Must be done prior to donation to ASF. > Versioning of mod_cluster management protocol (MCMP) > ---------------------------------------------------- > > Key: MODCLUSTER-454 > URL: https://issues.jboss.org/browse/MODCLUSTER-454 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java), Documentation & Demos, Native (httpd modules) > Affects Versions: 1.0.0.GA, 1.1.0.Final, 1.2.0.Final, 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > * Investigate the current state of MCMP versioning > * Design protocol version negotiation > * Must be done prior to donation to ASF -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-473) Describe Context#getPath contract when dealing with the root context

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-473?page=com.atlassian.jira.pl... ] Radoslav Husar closed MODCLUSTER-473. ------------------------------------- > Describe Context#getPath contract when dealing with the root context > -------------------------------------------------------------------- > > Key: MODCLUSTER-473 > URL: https://issues.jboss.org/browse/MODCLUSTER-473 > Project: mod_cluster > Issue Type: Enhancement > Components: Documentation & Demos > Affects Versions: 1.3.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 1.3.2.Alpha1 > > > Tomcat used "" to represent root context path, yet with undertow, the path is represented as "/". This is not handled well by modcluster. The container SPI could encapsulate the details of how the root context is treated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-477) Broken design: cookie-name should be specified on the Context level instead of only on the Engine level

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-477?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-477: -------------------------------------- Priority: Critical (was: Blocker) > Broken design: cookie-name should be specified on the Context level instead of only on the Engine level > ------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-477 > URL: https://issues.jboss.org/browse/MODCLUSTER-477 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java), Documentation & Demos, Native (httpd modules) > Affects Versions: 1.0.10, 1.1.3.Final, 1.2.11.Final, 1.3.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > In web.xml [2], user is allowed to configure cookie name per context. However, in MCMP [1] this configuration is only propagated on the CONFIG - org.jboss.modcluster.container.Engine level. > This essentially means that user configuring a cookie name different from the default / or default host configuration will have broken session stickiness. > [2] > https://developer.jboss.org/wiki/Mod-ClusterManagementProtocol > [1] > {code:xml} > <xsd:element name="name" > type="javaee:cookie-nameType" > minOccurs="0"> > <xsd:annotation> > <xsd:documentation> > The name that will be assigned to any session tracking > cookies created by this web application. > The default is JSESSIONID > > </xsd:documentation> > </xsd:annotation> > </xsd:element> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-477) Broken design: cookie-name should be specified on the Context level instead of only on the Engine level

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-477?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-477: ------------------------------------------------ Without rewriting the protocol and most of C code there is no way we can do that. > Broken design: cookie-name should be specified on the Context level instead of only on the Engine level > ------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-477 > URL: https://issues.jboss.org/browse/MODCLUSTER-477 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java), Documentation & Demos, Native (httpd modules) > Affects Versions: 1.0.10, 1.1.3.Final, 1.2.11.Final, 1.3.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > > In web.xml [2], user is allowed to configure cookie name per context. However, in MCMP [1] this configuration is only propagated on the CONFIG - org.jboss.modcluster.container.Engine level. > This essentially means that user configuring a cookie name different from the default / or default host configuration will have broken session stickiness. > [2] > https://developer.jboss.org/wiki/Mod-ClusterManagementProtocol > [1] > {code:xml} > <xsd:element name="name" > type="javaee:cookie-nameType" > minOccurs="0"> > <xsd:annotation> > <xsd:documentation> > The name that will be assigned to any session tracking > cookies created by this web application. > The default is JSESSIONID > > </xsd:documentation> > </xsd:annotation> > </xsd:element> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-477) Broken design: cookie-name should be specified on the Context level instead of only on the Engine level

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-477: ----------------------------------------- Summary: Broken design: cookie-name should be specified on the Context level instead of only on the Engine level Key: MODCLUSTER-477 URL: https://issues.jboss.org/browse/MODCLUSTER-477 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java), Documentation & Demos, Native (httpd modules) Affects Versions: 1.3.1.Final, 1.2.11.Final, 1.1.3.Final, 1.0.10 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Blocker In web.xml [2], user is allowed to configure cookie name per context. However, in MCMP [1] this configuration is only propagated on the CONFIG - org.jboss.modcluster.container.Engine level. This essentially means that user configuring a cookie name different from the default / or default host configuration will have broken session stickiness. [2] https://developer.jboss.org/wiki/Mod-ClusterManagementProtocol [1] {code:xml} <xsd:element name="name" type="javaee:cookie-nameType" minOccurs="0"> <xsd:annotation> <xsd:documentation> The name that will be assigned to any session tracking cookies created by this web application. The default is JSESSIONID </xsd:documentation> </xsd:annotation> </xsd:element> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues February 2016