You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Vikas <vi...@infravio.com> on 2006/02/09 14:44:46 UTC
IRC - Log (09-March-2006)
#apache-synapse
Soumadeep I think we should go with the SO concept...
pvikas hello everyone..
Soumadeep its becoming very difficult to handle mediator config files using a combo of adb,omelement and xpath..
pvikas does anybody have any concerns??
Soumadeep any thoughts?
-->| venkat (n=chatzill@220.225.137.194) has joined #apache-synapse
pvikas tried them both... OMElement doesn't have many utilities built around it ..
pvikas adb requires a schema, then classes, to be in place..
pvikas changing the xml implies regenerating the schema based classes..
Rajesh_Koilpilla I think you should checkin the samples demonstrating both approaches into the scratch area
Rajesh_Koilpilla So that folks can comment on it
Soumadeep That's a good idea...
Rajesh_Koilpilla Is there a sample which demonstrates JMX based mediation?
Rajesh_Koilpilla I know we have the mediator class - but can it be run out of the box?
Soumadeep Yeah
pvikas u mean the event generation part?
Rajesh_Koilpilla yes - with the available set of mediators
Rajesh_Koilpilla ?
Soumadeep But we need the MIX object
Soumadeep Management Information eXchange format
Soumadeep We still need to agree on the format...
Soumadeep awaiting response from the other folks...
Rajesh_Koilpilla plus the dependency which we have on AXIS2 to provide some of the base management information - right
Soumadeep Also we need to have a clear understanding of what we are going to do about the management interfaces
Soumadeep MIX will just capture the data, but then it needs to be instrumented
Rajesh_Koilpilla I think we could leverage what was proposed earlier by Mukund as for as the various subsystems are concerned (i.e discovery, events, metrics, state)
Soumadeep Yes,
Rajesh_Koilpilla We also need to build in the capability for each mediator to pump in it's own management information if there is any? so that the information transmitted can also be generic
pvikas it seems axis2's next release would be by monday and they are aiming for a final release soon..
Rajesh_Koilpilla is it 0.9.5 ?
pvikas ya 0.95
pvikas and the final release i.e. 2.1
karni What is the state here exactly, as proposed by mukund
Rajesh_Koilpilla we also need to make sure we have the provision to capture the following metrics
Rajesh_Koilpilla Total Hits (Mediation Runtime)
Rajesh_Koilpilla Total Hits (per proxy)
Rajesh_Koilpilla Successful Hits (per proxy)
pvikas [karni]i think, state = deployed, started, stopped, etc;
Rajesh_Koilpilla Failed Hits (per proxy)
Rajesh_Koilpilla Number of Mediator Policy Enforcement Failures (per proxy)
Rajesh_Koilpilla Incoming Message Size (per proxy)
Rajesh_Koilpilla Outgoing Message Size (per proxy)
Rajesh_Koilpilla Average Response Time (per proxy)
Rajesh_Koilpilla Last Response Time (per proxy)
Rajesh_Koilpilla Number of active consumers who are accessing the proxy
Rajesh_Koilpilla Hit Statistics by Consumer (i.e. total / failed / successful)
pvikas [rajesh] no. of active consumers accessing the proxy?
pvikas other things are statistics..gained over time
pvikas this one seems dynamic..
Rajesh_Koilpilla If we map this information to a consumer application - i.e the Consumer Identification Mediator
Rajesh_Koilpilla This could be as long as the VM is alive (dynamic information)
Rajesh_Koilpilla Do we have a running document which atleast captures this information
karni Throughput(per proxy) and if we can provision an faultcode (basic/routing/security).
pvikas and how do we interpret active consumers?
Rajesh_Koilpilla Yup, throughput is needed
Rajesh_Koilpilla It ain't active - consumers who are using the system from the time it went UP
pvikas oh..
Soumadeep some info that we proposed...
Soumadeep private String epr = null;
Soumadeep private String clientIP = null;
Soumadeep private String operation = null;
Soumadeep private String providerEPR = null;
pvikas so, classfying requests based on proxies and consumers also..
Soumadeep private String soapRequest = null;
Soumadeep private String soapResponse = null;
Soumadeep private Date timeStamp = null;
Soumadeep private long totalRoundtripTime = 0;
Soumadeep private long providerExecutionTime = 0;
Soumadeep private String transactionID = null;
Soumadeep private String userAgent = null;
Soumadeep private Collection mediatorExecTime = new ArrayList();
Rajesh_Koilpilla Soum - we should add the additional ones to the list which you have
pvikas so do we classify data as - Synapse data, service end-point data...
Rajesh_Koilpilla JMX 1.2 is bundled with Tomcat 5.x. We should start investigating dynamic MBean registration and issues related to their lifecycle and the persistent state maintained by them
Soumadeep yeah sure
Rajesh_Koilpilla What is Synapse data here?
Rajesh_Koilpilla most of the ones which we mentioned above are relevant to the proxy itself
-->| Hariharasudhan (n=hari@220.225.137.194) has joined #apache-synapse
Rajesh_Koilpilla Hi Harry :)
Soumadeep yeah
Hariharasudhan hi sorry iam late
pvikas Total Hits (Mediation Runtime)... mediationExecTime etc;
pvikas these are synapse related..
Rajesh_Koilpilla ok
pvikas nothing to do with proxy..
pvikas or the service-endpoint
Rajesh_Koilpilla Got to go now
Rajesh_Koilpilla Who is going to post this chat log?
|<-- Rajesh_Koilpilla has left irc.freenode.net ("ChatZilla 0.9.61 [Mozilla rv:1.7.2/20040803]")
Soumadeep bye guys...
|<-- Soumadeep has left irc.freenode.net ("ChatZilla 0.9.61 [Mozilla rv:1.7.2/20040803]")
|<-- venkat has left irc.freenode.net ("ChatZilla 0.9.61 [Mozilla rv:1.7.2/20040803]")
|<-- karni has left irc.freenode.net ("ChatZilla 0.9.61 [Mozilla rv:1.7.2/20040803]")