According to [1] there is not much performance degradation in normal JMX. But still I couldn't fine any literature describing the JMX notifications performance impact. I'll search more in to this.
In the endpoint case the notifications are sent only when the endpoint state changes. This occurs very rarely. If the endpoints change the states regularly there is something wrong in the system. So I think the performance impact will be minimal. Thanks, Supun.. [1] http://weblogs.java.net/blog/emcmanus/archive/2006/07/how_much_does_i.html On Wed, Dec 2, 2009 at 8:39 PM, indika kumara <indika.k...@gmail.com> wrote: > + 1 > > And ... is there any other places that this feature is useful ?. And > , just to get know , can this affect the run-time performance?. If so > , Can we do this using an asynchronous model ? > > Thanks > Indika > > On Thu, Dec 3, 2009 at 3:46 AM, Supun Kamburugamuva <supu...@gmail.com> > wrote: > > Hi, > > > > At the moment Synapse exposes endpoint statistics through JMX. In case of > > Endpoint state changes (i.e. marked as SUSPENDED) we can provide JMX > > notifications. This allows users to take actions promptly without waiting > > for pulling the endpoint status data. I would like to know the opinion of > > the community. The implementation is simple and if you agree on this I > can > > provide a patch. > > > > Thanks, > > Supun.. > > > > -- > > Software Engineer, WSO2 Inc > > http://wso2.org > > supunk.blogspot.com > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > For additional commands, e-mail: dev-h...@synapse.apache.org > > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
