[JBoss JIRA] (MODCLUSTER-11) Default LoadManager impl
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-11?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-11.
------------------------------------
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
> Default LoadManager impl
> ------------------------
>
> Key: MODCLUSTER-11
> URL: https://issues.jboss.org/browse/MODCLUSTER-11
> 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
>
>
> Default impl of the LoadManager interface. Should include a time-decay function so a history of metrics can be retained, with more recent values having greater weight in the overall load calculation.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-126) Microcontainer does not choose the right constructor when creating RequestCountLoadMetric
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-126?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-126.
-------------------------------------
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
> Microcontainer does not choose the right constructor when creating RequestCountLoadMetric
> -----------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-126
> URL: https://issues.jboss.org/browse/MODCLUSTER-126
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.3.GA, 1.1.0.Beta1
> Reporter: Takayoshi Kimura
> Assignee: Paul Ferraro
> Fix For: 1.0.4.GA, 1.1.0.CR1
>
> Attachments: modcluster-126.patch
>
>
> The MODCLUSTER-116 problem also applies to RequestCountLoadMetric, ReceiveTrafficLoadMetric and SendTrafficLoadMetric.
> DEPLOYMENTS IN ERROR:
> Deployment "RequestCountLoadMetric" is in error due to the following reason(s): **ERROR**, java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[org.jboss.modcluster.load.metric.DeterministicLoadState] actual=[org.jboss.modcluster.load.metric.impl.RequestProcessorLoadMetricSource]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-194) When encrypting the mod_cluster traffic, can't use the http connector
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-194?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-194.
-------------------------------------
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
> When encrypting the mod_cluster traffic, can't use the http connector
> ---------------------------------------------------------------------
>
> Key: MODCLUSTER-194
> URL: https://issues.jboss.org/browse/MODCLUSTER-194
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.0.Final
> Reporter: Samuel Mendenhall
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Fix For: 1.2.1.Beta1
>
>
> It would appear not possible to use the http connector when encrypting the mod_cluster connection. For mod_cluster to use the 8443 connector in JBoss, one has to comment out both the 8009 connector and 8080. But this raises a question, even if it were possible to keep the 8080 connector, it doesn't appear mod_cluster is able to hit both, as there would need to be multiple mod_cluster VHs in httpd.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-150) improve packaging so that the bundle can run in ~ too
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-150?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-150.
-------------------------------------
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
> improve packaging so that the bundle can run in ~ too
> -----------------------------------------------------
>
> Key: MODCLUSTER-150
> URL: https://issues.jboss.org/browse/MODCLUSTER-150
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: any
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Fix For: 1.1.0.CR2
>
>
> the bundles actually are excepted to be started in /opt/jboss/httpd/ in fact it would be nice that they also run in ~/httpd
> Additionally the quick start parameter should be in the httpd.conf (commented out may be) to ease testing.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-276) no training slash leads to 302
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-276?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-276.
-------------------------------------
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
> no training slash leads to 302
> ------------------------------
>
> Key: MODCLUSTER-276
> URL: https://issues.jboss.org/browse/MODCLUSTER-276
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Christoph Gostner
> Assignee: Jean-Frederic Clere
> Labels: clustering, http, jboss-as7, mod_cluster
>
> Setup and democlient are described in forum post.
> Apache httpd and AS7 are on the same VM with the name 'ci'.
> The internal mapping of the VM has a different name to make clear, that the JBoss instances aren't directly accessible.
> Calling 'http://ci:8000/demo7/' works as expected, but without the trailing slash (http://ci:8000/demo7) a 303 error happens. The browser gets a redirect to an internal URL http://cluster:8080/demo7/ which of course is not accessible.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-30) {HA}ModClusterService: advertisePort uses incorrect system property
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-30?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-30.
------------------------------------
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
> {HA}ModClusterService: advertisePort uses incorrect system property
> -------------------------------------------------------------------
>
> Key: MODCLUSTER-30
> URL: https://issues.jboss.org/browse/MODCLUSTER-30
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 1.0.0.Beta3
>
>
> <property name="advertisePort">${jboss.modcluster.advertise.address:23364}</property>
> uses the multicast address rather than port. I'm changing this to
> <property name="advertisePort">${jboss.modcluster.advertise.port:23364}</property>
> in both ModClusterService and HAModClusterService
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months