On Wed, 2007-10-31 at 17:44 +0530, Asankha C. Perera wrote:
> Hi Odi
> > You are touching an important subject: lifecycle management. I suggest
> > create, start, stop, destroy methods in some classes/APIs (semantics of
> > JBoss Service MBeans). I think it's vital that we support that. Would
> > you mind opening a JIRA ticket for this?
> >   
> I opened an improvement request 
> (http://issues.apache.org/jira/browse/HTTPCORE-127) so that we can 
> officially queue this for consideration
> > JMX is a JDK 1.5 API (or J2EE 1.4). This would change the 1.3 dependency
> > requirement. I think it's best to implement the JMX stuff at the Synapse
> > level at the moment. You know best what you need. Maybe later we can
> > incorporate that into a separate module, if it's of interest to other users.
> >   
> +1
> We will handle this at the Synapse transport level for now
> 
> thanks
> asankha
> 

Asankha

We already collect some metrics in HttpCore:  

http://svn.apache.org/repos/asf/jakarta/httpcomponents/httpcore/trunk/module-main/src/main/java/org/apache/http/io/HttpTransportMetrics.java

http://svn.apache.org/repos/asf/jakarta/httpcomponents/httpcore/trunk/module-main/src/main/java/org/apache/http/HttpConnectionMetrics.java

We could introduce additional interfaces for I/O reactor specific
metrics. This way one could easily expose these metrics through an JMX
compliant extension with just a little bit of custom code.

Oleg   


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to