Hi Asanka, I see couple of problems in the log:
Looks like you have deployed an invalid partition: Caused by: org.apache.stratos.cloud.controller.exception.InvalidPartitionException: Partition is not valid: [partition-id] partition-1 May be you have not defined the IaaS providers in the network partition definition: Caused by: org.apache.stratos.cloud.controller.exception.CloudControllerException: Partition [partition-2] validation failed. Partition provider is null. May be message broker was not available: javax.jms.JMSException: Could not connect to broker URL: tcp:// 127.0.0.1:61616. Reason: java.net.ConnectException: Connection refused In addition to the above errors did you wait until the topology get initialized before deploying the artifacts? Thanks On Fri, Mar 27, 2015 at 11:13 PM, Asanka Sanjaya Herath <[email protected]> wrote: > I have used the sample script provided by stratos in order to deploy the > application on ec-2. > I have attached the carbon log here. > > On Thu, Mar 26, 2015 at 6:24 PM, Imesh Gunaratne <[email protected]> wrote: > >> Hi Asanka, >> >> Thanks for reporting this. Will you be able to post the artifacts you >> used and the carbon log? >> >> Thanks >> >> On Wed, Mar 25, 2015 at 11:59 PM, Asanka Sanjaya Herath < >> [email protected]> wrote: >> >>> Hi All, >>> >>> I noticed an issue with stratos master branch. I deployed an >>> application in ec-2 and that worked well. Then I restarted stratos. Now >>> stratos is acting like there is no any application is deployed. The console >>> has stopped in "Application status event message delegator started". >>> >>> Thanks. >>> >>> -- >>> Thanks, >>> Regards, >>> ASH >>> >> >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > > > -- > Thanks, > Regards, > ASH > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
