[JBoss JIRA] Created: (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
9:13 p.m.
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
Where there exists:
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:18 p.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
[
https://issues.jboss.org/browse/MODCLUSTER-151?page=com.atlassian.jira.pl...
]
Radoslav Husar updated MODCLUSTER-151:
--------------------------------------
Original Estimate: 2 days
Remaining Estimate: 2 days
Issue Type: Bug (was: Feature Request)
Affects Version/s: 1.1.3.Final
Description:
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
{code}
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
{code}
Where there exists:
{code}
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
{code}
The various jbossweb load metrics would use this source.
was:
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
Where there exists:
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
The various jbossweb load metrics would use this source.
Upgrading as this is a bug in AS7.
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://issues.jboss.org/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR1, 1.1.3.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Original Estimate: 2 days
Remaining Estimate: 2 days
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
{code}
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
{code}
Where there exists:
{code}
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
{code}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:03 p.m.
New subject: [JBoss JIRA] (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
[
https://issues.jboss.org/browse/MODCLUSTER-151?page=com.atlassian.jira.pl...
]
Michal Babacek commented on MODCLUSTER-151:
-------------------------------------------
*Fix Version/s: * ??? Aren't we gonna need it soon for EAP6...?
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://issues.jboss.org/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR1, 1.1.3.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Original Estimate: 2 days
Remaining Estimate: 2 days
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
{code}
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
{code}
Where there exists:
{code}
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
{code}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:03 p.m.
New subject: [JBoss JIRA] (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
[
https://issues.jboss.org/browse/MODCLUSTER-151?page=com.atlassian.jira.pl...
]
Michal Babacek edited comment on MODCLUSTER-151 at 12/2/11 8:03 AM:
--------------------------------------------------------------------
*Fix Version/s:* ??? Aren't we gonna need it soon for EAP6...?
was (Author: mbabacek):
*Fix Version/s: * ??? Aren't we gonna need it soon for EAP6...?
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://issues.jboss.org/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR1, 1.1.3.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Original Estimate: 2 days
Remaining Estimate: 2 days
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
{code}
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
{code}
Where there exists:
{code}
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
{code}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 p.m.
New subject: [JBoss JIRA] (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
[
https://issues.jboss.org/browse/MODCLUSTER-151?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-151:
-------------------------------------------
Fix Version/s: 1.2.0.Beta1
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://issues.jboss.org/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR1, 1.1.3.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 1.2.0.Beta1
Original Estimate: 2 days
Remaining Estimate: 2 days
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
{code}
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
{code}
Where there exists:
{code}
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
{code}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 p.m.
New subject: [JBoss JIRA] (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
[
https://issues.jboss.org/browse/MODCLUSTER-151?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-151:
-------------------------------------------
Fix Version/s: 1.2.0.Beta2
(was: 1.2.0.Beta1)
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://issues.jboss.org/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR1, 1.1.3.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 1.2.0.Beta2
Original Estimate: 2 days
Remaining Estimate: 2 days
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
{code}
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
{code}
Where there exists:
{code}
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
{code}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 p.m.
New subject: [JBoss JIRA] (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
[
https://issues.jboss.org/browse/MODCLUSTER-151?page=com.atlassian.jira.pl...
]
Paul Ferraro resolved MODCLUSTER-151.
-------------------------------------
Fix Version/s: 1.2.0.Beta1
(was: 1.2.0.Beta2)
Resolution: Done
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://issues.jboss.org/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR1, 1.1.3.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 1.2.0.Beta1
Original Estimate: 2 days
Remaining Estimate: 2 days
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric,
BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric,
SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server.
Really, this should be scoped to an engine. While server:engine is usually a 1:1
relationship, this is technically a 1:N relationship.
Suggested API change:
{code}
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
{code}
Where there exists:
{code}
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
{code}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4522
days inactive
5104
days old
mod_cluster-issues@lists.jboss.org
6 comments
6 participants
participants (6)
-
Jean-Frederic Clere (Updated) (JIRA) -
Michal Babacek (Commented) (JIRA)
-
Michal Babacek (Issue Comment Edited) (JIRA)
-
Paul Ferraro (JIRA)
-
Paul Ferraro (Resolved) (JIRA)
-
Radoslav Husar (JIRA)