Hi Ramindu, Thanks for the fix.
Regards, Megala On Fri, Dec 16, 2016 at 4:30 PM, Ramindu De Silva <ramin...@wso2.com> wrote: > Hi Megala, > > This was due to a recent change in viewing execution plans. > I have added the fix in commit [1] > > 1. https://github.com/wso2/carbon-event-processing/pull/271 > > Best Regards, > > On Fri, Dec 16, 2016 at 9:29 AM, Damith Wickramasinghe <dami...@wso2.com> > wrote: > >> Hi Ramindu, >> >> AFAIK having upcount triggered in corresponding extensions init method >> should solve this. Since it should be happen once. We need to see why its >> triggering every time we views the execution plan. Were you able to check >> on it. >> >> Regards, >> Damith. >> >> >> >> On Fri, Dec 16, 2016 at 8:28 AM, Ramindu De Silva <ramin...@wso2.com> >> wrote: >> >>> Hi Megala, >>> >>> Yes, I'm experiencing the same. It is a bug. Will get back to you with a >>> fix or a workaround. Thanks for reporting the bug. >>> >>> @Damith, the execution plan up count is called even when viewing the >>> execution plans. And it makes the execution plan count increased by one. As >>> a fix, I think, we need to handle the call method call or will have to keep >>> a list of already available execution plans and check before increasing the >>> number. WDYT? >>> >>> Thanks, >>> >>> >>> On Thu, Dec 8, 2016 at 1:43 PM, Megala Uthayakumar <meg...@wso2.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> We are working on adding geo-fencing capabilities for IOT. While doing >>>> that we came across following problem intermittently. >>>> Sometimes the event fails to go from org.wso2.geo.ProcessedSpatialE >>>> vents:1.0.0 to org.wso2.geo.FusedSpatialEvent:1.0.0 and >>>> org.wso2.geo.AlertsNotifications:1.0.0 >>>> >>>> While debugging we found that the events are passed to EventFusion >>>> function and waiting on buffer to get the number of events that is >>>> equal to the deployed execution count, But the value shown for the deployed >>>> count is larger than the actual execution plan count. Further I found >>>> the deployed execution count increases whenever we click on the >>>> execution plan that is subscribed to geoDashboard in the carbon management >>>> console. The counts become to actual count after we restart the server. Is >>>> this a known bug ? Is there any work around solve this problem without >>>> restarting the server. >>>> >>>> Thanks. >>>> >>>> Regards, >>>> Megala >>>> -- >>>> Megala Uthayakumar >>>> >>>> Software Engineer >>>> Mobile : 0779967122 >>>> >>> >>> >>> >>> -- >>> *Ramindu De Silva* >>> Software Engineer >>> WSO2 Inc.: http://wso2.com >>> lean.enterprise.middleware >>> >>> email: ramin...@wso2.com <sanj...@wso2.com> >>> mob: +94 772339350 >>> mob: +94 719678895 >>> >> >> >> >> -- >> Software Engineer >> WSO2 Inc.; http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> lean.enterprise.middleware >> >> mobile: *+94728671315 <+94%2072%20867%201315>* >> >> > > > -- > *Ramindu De Silva* > Software Engineer > WSO2 Inc.: http://wso2.com > lean.enterprise.middleware > > email: ramin...@wso2.com <sanj...@wso2.com> > mob: +94 772339350 > mob: +94 719678895 > -- Megala Uthayakumar Software Engineer Mobile : 0779967122
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
