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
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
