[JBoss JIRA] (MODCLUSTER-217) request hang with a node is stop in EC2
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-217?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-217.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> request hang with a node is stop in EC2
> ---------------------------------------
>
> Key: MODCLUSTER-217
> URL: https://issues.jboss.org/browse/MODCLUSTER-217
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: EC2
> Reporter: Jean-Frederic Clere
> Assignee: Michal Babacek
> Priority: Minor
> Fix For: MOD_CLUSTER_1_0_10_GA_CP01, 1.1.3.Final
>
>
> Once stopping the EC2 the socket is closed so the cping doesn't wait for ping but connectiontimeout which default to nodeTimeout and/or server timeout.
> That affects only the first request (per process) once the node has been cleaned.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-118) character ? in
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-118?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-118.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> character ? in
> ---------------
>
> Key: MODCLUSTER-118
> URL: https://issues.jboss.org/browse/MODCLUSTER-118
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.0.GA, 1.1.0.Beta1
> Environment: Windows 7 Ultimate, Apache 2.2.14 , JBoss web/Tomcat configuration
> Reporter: Dmitry Sanatin
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.9, 1.1.0.CR1
>
> Attachments: patch.txt
>
>
> URI of http request is truncated up to '?' character at apache side. Cluster node receive wrong request. . If '?' is replaced by '%3f', it is passed to jboss "correctly".
> There is no such problem with 1.0.2 GA version.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-89) Alias from webapps/jboss-web.xml are not handled correctly in mod_cluster
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-89?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-89.
------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Alias from webapps/jboss-web.xml are not handled correctly in mod_cluster
> -------------------------------------------------------------------------
>
> Key: MODCLUSTER-89
> URL: https://issues.jboss.org/browse/MODCLUSTER-89
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.1.GA
> Environment: JBossas and application with a virtual-host in jboss-web.xml and the virtual-host doesn't correspond to an Alias in server.xml
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.2.GA, 1.1.0.Beta1
>
>
> Use <virtual-host>cluster.domain.com</virtual-host> in jboss-web.xml don't define the corresponding Alias in server.xml
> In server.log you have:
> 2009-08-03 17:49:27,208 WARN [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) Failed
> to map vhost: cluster.domain.com
> and mod_cluster ignores the application until you restart it and restart mod_cluster
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-125?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-125.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Permanently remove a JBoss node from configured http proxies
> ------------------------------------------------------------
>
> Key: MODCLUSTER-125
> URL: https://issues.jboss.org/browse/MODCLUSTER-125
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.3.GA, 1.1.0.Beta1, 1.1.0.CR1
> Reporter: Ben Schofield
> Assignee: Paul Ferraro
> Fix For: 1.1.0.CR1
>
>
> When a JBoss node is restarted it advertises the web apps deployed to it as being available for the http proxy to route traffic to them. This is undesirable when a JBoss administrator needs to keep a JBoss node out of service for validation and/or troubleshooting steps. Mod_cluster needs to offer some mechanism to permanently remove a JBoss node from any configured http proxy until a JBoss administrator manually adds it back.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-190) mod_cluster issues an ENABLE-APP too early in the webapp lifecycle
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-190?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-190.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> mod_cluster issues an ENABLE-APP too early in the webapp lifecycle
> ------------------------------------------------------------------
>
> Key: MODCLUSTER-190
> URL: https://issues.jboss.org/browse/MODCLUSTER-190
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.4.GA, 1.0.5, 1.1.0.Final
> Reporter: Samuel Mendenhall
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.5, 1.0.6, 1.1.1.Final
>
> Attachments: mod_cluster.patch
>
>
> mod_cluster uses START_EVENT instead of AFTER_START_EVENT so it might ENABLE the application too early.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-158) Avoid unnecessary open sockets for non-master nodes
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-158?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-158.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Avoid unnecessary open sockets for non-master nodes
> ---------------------------------------------------
>
> Key: MODCLUSTER-158
> URL: https://issues.jboss.org/browse/MODCLUSTER-158
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.3.GA, 1.1.0.CR2
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 1.0.4.GA, 1.1.0.CR3
>
>
> When a node is being reset, or when it first comes online, an INFO request is sent to the proxy. If this node is not the HASingleton master, this socket connection will typically remain open, unused, until it times out. We ought to proactively close this connection.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-197) Windows x86 Missing httpd.conf + other files in 1.1.0 distribution
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-197?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-197.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Windows x86 Missing httpd.conf + other files in 1.1.0 distribution
> ------------------------------------------------------------------
>
> Key: MODCLUSTER-197
> URL: https://issues.jboss.org/browse/MODCLUSTER-197
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.0.Final
> Environment: Windows x86
> Reporter: Greg Zoller
> Assignee: Jean-Frederic Clere
>
> According to the docs mod_cluster ships with a preconfigured httpd instance: just unpack and run.
> Unfortunately the Windows x86 version doesn't include all the conf files set up as the Linux distribution appears to have.
> These files need to be added or the documentation amended to reflect this.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-216) Second attempt to connect from Jboss to apache module sends incomplete Host Header
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-216?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-216.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Second attempt to connect from Jboss to apache module sends incomplete Host Header
> ----------------------------------------------------------------------------------
>
> Key: MODCLUSTER-216
> URL: https://issues.jboss.org/browse/MODCLUSTER-216
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.1.Final
> Reporter: Rui Alves
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Fix For: 1.1.2.Final
>
>
> It was detected that in an eventual second attempt from jboss AS to connect to apache module, the http 1.1 host header is incomplete.
> It seams to me that in DefaultMCMPHandler class the second "sendRequest" should have the "proxyhead" variable as parameter and not the "head" variable.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-10) Define API and SPI for the LoadManager
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-10?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-10.
------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Define API and SPI for the LoadManager
> --------------------------------------
>
> Key: MODCLUSTER-10
> URL: https://issues.jboss.org/browse/MODCLUSTER-10
> Project: mod_cluster
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Clustering, Web (Tomcat) service
> Reporter: Brian Stansberry
> Assignee: Paul Ferraro
> Fix For: JBossAS-5.1.0.Beta1
>
>
> Operation(s) it will expose to the component that periodically requests load; registration SPI for subcomponents that provide metrics, any configuration properties (e.g. for a time decay function).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-114) move the web site to magnolia
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-114?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-114.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> move the web site to magnolia
> -----------------------------
>
> Key: MODCLUSTER-114
> URL: https://issues.jboss.org/browse/MODCLUSTER-114
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: The web site needs to be migrated.
> Reporter: Jean-Frederic Clere
> Assignee: Ryszard Kozmik
> Fix For: 1.1.0.CR1
>
>
> shell scripts will be used for downloads and docs. Docs will be reviewed and edited by hands.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months