[JBoss JIRA] (MODCLUSTER-483) Support IPv6 addresses with zone indices across all implementations
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-483?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-483:
--------------------------------------
Description:
Java client
* fails with:
{noformat}
10:52:30,981 ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000042: Error null sending INFO command to 2620:52:0:105f:405a:77ff:fed5:8555%eth0.1/2620:52:0:105f:405a:77ff:fed5:8555%eth0.1:8484, configuration will be reset: null
{noformat}
Undertow LB
* does not format address properly and is not parsed at all
* in an open fix the zone id is removed completely
apache LB
* seems to never send zone indices
> Support IPv6 addresses with zone indices across all implementations
> -------------------------------------------------------------------
>
> Key: MODCLUSTER-483
> URL: https://issues.jboss.org/browse/MODCLUSTER-483
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.3.1.Final
> Reporter: Radoslav Husar
> Assignee: Jean-Frederic Clere
>
> Java client
> * fails with:
> {noformat}
> 10:52:30,981 ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000042: Error null sending INFO command to 2620:52:0:105f:405a:77ff:fed5:8555%eth0.1/2620:52:0:105f:405a:77ff:fed5:8555%eth0.1:8484, configuration will be reset: null
> {noformat}
> Undertow LB
> * does not format address properly and is not parsed at all
> * in an open fix the zone id is removed completely
> apache LB
> * seems to never send zone indices
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[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 edited comment on MODCLUSTER-454 at 3/2/16 3:48 PM:
-------------------------------------------------------------------
The VERSION method [1] was added via MODCLUSTER-409 but there is currently nothing else, the documentation/contract, versioning strategy, handling in Java does not exist.
The reponse looks like this:
{noformat}
[rhusar@syrah ~]$ curl -XVERSION http://127.0.0.1:9090 -H "Accept: text/xml"
<?xml version="1.0" standalone="yes" ?>
<version><release>mod_cluster/1.3.2.Alpha1-SNAPSHOT</release><protocol>0.2.1</protocol></version>
{noformat}
or
{noformat}
[rhusar@syrah ~]$ telnet ::1 9090
Trying ::1...
Connected to localhost.
Escape character is '^]'.
VERSION
release: mod_cluster/1.3.2.Alpha1-SNAPSHOT, protocol: 0.2.1
Connection closed by foreign host.
{noformat}
There is no mention of protocol version 0.2.1 even in the protocol page! https://developer.jboss.org/wiki/Mod-ClusterManagementProtocol
[1] https://github.com/modcluster/mod_cluster/commit/f020096983bab3ae0b71565c...
was (Author: rhusar):
The VERSION method [1] was added via MODCLUSTER-409 but there is currently nothing else, the documentation/contract, versioning strategy, handling in Java does not exist.
The reponse looks like this:
{noformat}
[rhusar@syrah ~]$ telnet ::1 9090
Trying ::1...
Connected to localhost.
Escape character is '^]'.
VERSION
release: mod_cluster/1.3.2.Alpha1-SNAPSHOT, protocol: 0.2.1
Connection closed by foreign host.
{noformat}
There is no mention of protocol version 0.2.1 even in the protocol page! https://developer.jboss.org/wiki/Mod-ClusterManagementProtocol
[1] https://github.com/modcluster/mod_cluster/commit/f020096983bab3ae0b71565c...
> 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
[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
[JBoss JIRA] (MODCLUSTER-478) session drain wait does not end for JBossWeb 7
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-478?page=com.atlassian.jira.pl... ]
Jean-Frederic Clere reassigned MODCLUSTER-478:
----------------------------------------------
Assignee: Radoslav Husar (was: Jean-Frederic Clere)
> 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: Radoslav Husar
>
> 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