Re: Framework for recording Axis2 latency statistics

On Wed, Jul 13, 2011 at 6:29 PM, Deepal Jayasinghe wrote: > I partially agree with you for the out going path, but for the > incoming path there is no streaming it just creates the Axiom object > by pointing to input stream. > > Application server likes Tomcat handle this, I am not 100% sure how >

Re: Framework for recording Axis2 latency statistics

Hi, Will study how Tomcat handles this. No abstract method will be added to AbstractTransportListener/Sender. Only getLatencyRecorder(), a concrete method, will be introduced to those classes so that all transport listeners/senders can use that method to obtain the LatencyRecorder object from the

Re: Framework for recording Axis2 latency statistics

I partially agree with you for the out going path, but for the incoming path there is no streaming it just creates the Axiom object by pointing to input stream. Application server likes Tomcat handle this, I am not 100% sure how they do that, but it is useful to understand their approaches as well

[jira] [Created] (AXIS2-5093) Connection cannot be cleaned up after 404 response

Connection cannot be cleaned up after 404 response -- Key: AXIS2-5093 URL: https://issues.apache.org/jira/browse/AXIS2-5093 Project: Axis2 Issue Type: Bug Components: transports A

Re: Framework for recording Axis2 latency statistics

Actually doing this at the handler level is the easiest thing. But it is not sufficient for a real production system where these parameters are critical for figuring out the system performance. There are many things happen at the transports like streaming, buffering etc. With a handler level imple

Re: Framework for recording Axis2 latency statistics

I agree with Azeez, this has to be done with handler. I do not like the idea of keep changing the abstract transport listener (in fact I am -1 on that). This is a nice feature but you need to make sure that you do not break anything. So, implement this feature using handlers, we have done similar

Re: Framework for recording Axis2 latency statistics

Why not introduce two handlers which will do this, and make those handlers sit right at the top of the in-flow, and right at the back of the outflow. That way, nothing has to be changed, and transports listeners/senders don't have to be changed, and you don't have to depend on the transport listene

Re: Framework for recording Axis2 latency statistics

Hi, On Wed, Jul 13, 2011 at 1:23 PM, Sagara Gunathunga < sagara.gunathu...@gmail.com> wrote: > +1 > > Sadeep , I have few questions > > 1.) Is it possible to make your framework pluggable ? I mean users can > enable and disable this feature. Yes, user can enable/disable this feature using axis2

[Axis2] Clustering guide is obsolete!

http://axis.apache.org/axis2/java/core/docs/clustering-guide.html is obsolete! I just came across this after a user asked a related question on the synapse-user list. I will try to find some time to update it. In the mean time, the following articles can be used as a reference, if required. http:

Re: Framework for recording Axis2 latency statistics

+1 Sadeep , I have few questions 1.) Is it possible to make your framework pluggable ? I mean users can enable and disable this feature. 2.) Can you explain bit of a implementation level details of your suggestion ? Whether you use Observer like pattern to collect those statistics ? Thanks ! O