March 2013 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-331) Add mod_cluster container SPI implementation for undertow

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-331?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-331: ------------------------------------------- WIP implementation PR: https://github.com/undertow-io/jboss-as/pull/1 > Add mod_cluster container SPI implementation for undertow > --------------------------------------------------------- > > Key: MODCLUSTER-331 > URL: https://issues.jboss.org/browse/MODCLUSTER-331 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 1.2.4.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-315: ------------------------------------------- No & no. Fix version is 1.2.4.Final (to be released) and both latest EAP/AS use only version 1.2.3.Final. > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: James Perkins > Assignee: Paul Ferraro > Fix For: 1.2.4.Final > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Dimitris Andreadis commented on MODCLUSTER-315: ----------------------------------------------- Okay, now I am confused. Is this in EAP 6.1 and upstream in AS8? > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: James Perkins > Assignee: Paul Ferraro > Fix For: 1.2.4.Final > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-282) Add JGRoups support

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-282?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-282: ------------------------------------------- Fix Version/s: 1.3.0.Alpha1 (was: 1.2.1.Beta2) > Add JGRoups support > ------------------- > > Key: MODCLUSTER-282 > URL: https://issues.jboss.org/browse/MODCLUSTER-282 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.0.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.3.0.Alpha1 > > > https://community.jboss.org/wiki/MOD-CLUSTERDiscoveryProtocol -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-288) SystemMemoryUsageLoadMetric is not correct on Linux/Unix

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-288?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-288. -------------------------------------------- Resolution: Won't Fix it is not possible to fix that without adding some JNI code to the JVM... > SystemMemoryUsageLoadMetric is not correct on Linux/Unix > -------------------------------------------------------- > > Key: MODCLUSTER-288 > URL: https://issues.jboss.org/browse/MODCLUSTER-288 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.0.10, 1.1.0.Final, 1.1.1.Final, 1.2.0.Final > Environment: Linux/Unix operating systems with standard memory management > Reporter: Michal Babacek > Assignee: Paul Ferraro > > I am convinced that the [SystemMemoryUsageLoadMetric.java|https://github.com/modcluster/mod_cluste...] is of no use to anyone. > I have tested it by allocating some memory outside the JVM control with [NativeMemoryStress.c|https://github.com/Karm/clusterbench/blob/system-mem...]. > The results from Mod_cluster are such that the system is almost fully loaded all the time despite the fact that I work with 8GB RAM box with almost nothing running on it. > This [picture|http://hudson.qa.jboss.com/hudson/view/mod_cluster-QE/view/mod_cl...] displays time on X axis and (100-(Load from Mod_cluster)) on Y axis. As you may observe, all 4 nodes appear to be under full load all the time and there is a spike on each of them. This spike represents a period of time when the aforementioned [NativeMemoryStress.c|https://github.com/Karm/clusterbench/blob/system-mem...] was called with the following setting: > {noformat} > megabytes 500; > milliseconds 60000; > {noformat} > What had happened is that kernel has cleared some cache and garbage data from the RAM in order to accommodate new demands, so by the time I freed the memory, there was all of sudden actually more free RAM then before. > The actual problem with the current [SystemMemoryUsageLoadMetric.java|https://github.com/modcluster/mod_cluste...] implementation using [OperatingSystemMXBean|http://docs.oracle.com/javase/6/docs/jre/api/manage...] is that this code: > {code:lang=java} > +++ > public static final String FREE_MEMORY = "FreePhysicalMemorySize"; > public static final String TOTAL_MEMORY = "TotalPhysicalMemorySize"; > +++ > double free = ((Number) this.server.getAttribute(name, FREE_MEMORY)).doubleValue(); > double total = ((Number) this.server.getAttribute(name, TOTAL_MEMORY)).doubleValue(); > return (total - free) / total; > +++ > {code} > Is somewhat similar to this (on 8GB RAM machine with almost nothing running on at the moment): > {noformat} > [karm@killerbox karm]$ free -m > total used free shared buffers cached > Mem: 7933 6755 1177 0 44 141 > -/+ buffers/cache: 6569 1363 > Swap: 16383 58 16325 > {noformat} > Obviously, this does not mean that I could get only 1177MB of RAM if I want to. The "free" actually means "wasted". The majority of RAM is being used as cache. If I ask for e.g. 2GB, I am gonna get them, because kernel will simply sacrifice some cache, clears some garbage from RAM and free up space so as to accommodate my demands. > So, according to my opinion, on a sane, well-behaving caching operating system, the [SystemMemoryUsageLoadMetric.java|https://github.com/modcluster/mod_cluste...] will always show ~ 98% RAM usage. > Due to this fact, this metric is unlikely to be of some use to anyone on Linux/UNIX. What do you think? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Radoslav Husar resolved MODCLUSTER-315. --------------------------------------- Resolution: Done > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: James Perkins > Assignee: Paul Ferraro > Fix For: 1.2.4.Final > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-315: ------------------------------------------- Also, I suggest lets move master to 1.3 so we avoid similar confusion: https://github.com/modcluster/mod_cluster/pull/13 > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: James Perkins > Assignee: Paul Ferraro > Fix For: 1.2.4.Final > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Radoslav Husar reopened MODCLUSTER-315: --------------------------------------- > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-315: -------------------------------------- Issue Type: Feature Request (was: Task) Fix Version/s: 1.2.4.Final Git Pull Request: https://github.com/modcluster/mod_cluster/pull/3, https://github.com/modcluster/mod_cluster/pull/12 Affects Version/s: 1.2.3.Final (updating fix version) > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: James Perkins > Assignee: Paul Ferraro > Fix For: 1.2.4.Final > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-315: ------------------------------------------------ ok I have merged the plug request. > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues March 2013