Hi, This is resolved with Raj's commit in [1]. I've tested and verified in OpenStack setup.
[1] https://github.com/apache/stratos/commit/bf4335b1ef60b4ea596ee3b14960deac5a8e55fe Thanks. On Wed, Nov 18, 2015 at 7:58 PM, Gayan Gunarathne <gay...@wso2.com> wrote: > Hi All, > > If we summarize issues mention in this thread, > > Issue 1 - This is happen if Stratos is restarting before application get > activated.(If application is in the initiate state). If anyone experience > this issue after the application activation? > > Issue 2 - Regarding the Axis2 exception, seems it is a intermittent > issue.As this is happened in the restart, it will be happened due to > limitation of the maximum connection in the axis2 service as per[1].If this > happen regularly I think better if we can set the limits on maximum > connections. > > [1] https://issues.apache.org/jira/browse/AXIS2-4807 > > Thanks, > Gayan > > On Wed, Nov 18, 2015 at 2:26 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi Akila, >> >> Yes, I am aware of component synchronization. But the logs suggests that >> there is a communication issue between AS & CC while AS tries to validate >> deployment policy as part of cluster monitor creation. It doesn't >> necessarily mean that CC was not started before AS (as per the logs, we can >> easily see that CC was started before AS). There can be some other >> communication issues as described here [1]. >> >> So are we sure that the above exception was not thrown while AS tried to >> validate the deployment policy with CC as part of cluster monitor creation? >> >> [1] https://issues.apache.org/jira/browse/AXIS2-4807 >> >> Thanks, >> Raj. >> >> On Wed, Nov 18, 2015 at 2:15 PM, Akila Ravihansa Perera < >> raviha...@wso2.com> wrote: >> >>> Hi Raj, >>> >>> There is a component startup order which will make sure CC, AS and SM >>> are ready before accepting any request from Stratos API. >>> >>> On Wed, Nov 18, 2015 at 12:52 PM, Rajkumar Rajaratnam < >>>>> rajkum...@wso2.com> wrote: >>>>> >>>>>> Hi Pubudu, >>>>>> >>>>>> In your case, the monitors are not started/scheduled after server >>>>>> restart because of the following error. There seems to be a communication >>>>>> issue between AS and CC, may be CC web service was not ready at that >>>>>> time. >>>>>> >>>>> >>> CC must be available when AS is creating monitors as per component >>> synchronizer implementation. If it is not then that's a different issue. >>> >>> Thanks. >>> >>> >> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> > > > > -- > > Gayan Gunarathne > Technical Lead, WSO2 Inc. (http://wso2.com) > Committer & PMC Member, Apache Stratos > email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985> > > > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
