Hi Pranavan, What events are you expecting here?
Either you need to deploy an application to receive events OR write your own custom thrift client to publish events to CEP. What is your approach to test the curve fitting window processor? My suggestion is to write your own thrift client which would publish predefined sets of events and check whether curve fitting window processor is calculating the correct values for those event sets. After that you can deploy an application on mock iaas and test the end-to-end flow. You can define a range of values to be published In mock iaas as well. On Sun, Aug 9, 2015 at 9:00 PM, Pranavan Theivendiram < pranavan...@cse.mrt.ac.lk> wrote: > Hi All, > > I have completed the window processor for curve fitting and during the > manual testing I found that its run method is called (I have put some info > logs and they are printed for every 10 minutes) as expected. But it does > not calculate the curve fitting co-efficient since the events are not > received by CEP. In order to check whether it is the problem from my > implementation, I have checked whether the events are received by other > window processors such as gradient and second gradient, they also do not > receive the new events. In management console I also checked whether the > execution plans and event streams are active. They are active as expected. > What is the reason behind this ? Is this normal? > > Thank you > > Regards, > *T. Pranavan* > *BSc Eng Undergraduate| Department of Computer Science & Engineering > ,University of Moratuwa* > *Mobile| *0775136836 > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
