Re: Refactoring Event Receivers in Messaging Component

2015-12-24 Thread Isuru Haththotuwa
This is now completed and pushed to stratos-4.1.x and master branch. On Sat, Dec 5, 2015 at 9:36 PM, Imesh Gunaratne wrote: > +1 for the suggestion Isuru! This would improve the time it takes to > handle locks and also would not print warning logs for already processed > events. > > Thanks > > O

Re: Refactoring Event Receivers in Messaging Component

2015-12-05 Thread Imesh Gunaratne
+1 for the suggestion Isuru! This would improve the time it takes to handle locks and also would not print warning logs for already processed events. Thanks On Fri, Dec 4, 2015 at 5:19 AM, Isuru Haththotuwa wrote: > Hi Devs, > > Started doing $subject. The Event Receiver model was designed when

Refactoring Event Receivers in Messaging Component

2015-12-03 Thread Isuru Haththotuwa
Hi Devs, Started doing $subject. The Event Receiver model was designed when Stratos cannot be run on a single JVM, and it was not properly re-factored once the Stratos single JVM distribution came up. So, all the main components (Stratos Manager, Cloud Controller, Autoscaler) has their own Message