[
https://issues.apache.org/jira/browse/STRATOS-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217536#comment-14217536
]
Isuru Haththotuwa commented on STRATOS-986:
-------------------------------------------
Hi Martin,
In your startup order, you have specified the following:
1. "cartridge.c2,cartridge.c1",
2. "cartridge.c3,cartridge.c2"
AFAIU, this means the following:
1. start c2, then c1
2. start c3 then c2
AFAIU this means, start c3, then c2, then c1. So you can specify the rules as
below:
"cartridge.c3,cartridge.c2,cartridge.c1",
Can you try with the same?
Please note that this issue is related to [1]. Reka has already done some
improvements to detect this in the app definition.
[1]. https://issues.apache.org/jira/browse/STRATOS-984
> no startup of VMs scenario 2
> ----------------------------
>
> Key: STRATOS-986
> URL: https://issues.apache.org/jira/browse/STRATOS-986
> Project: Stratos
> Issue Type: Bug
> Reporter: Martin Eppel
> Attachments: application_test_app5b.json, group5.json,
> wso2carbon.log.gz
>
>
> Slightly different configuration as jira 984
> Expected behavior is that 1. c3, 2. c2, 3. c1 starts up
> Observed beahvior: no VM is started up
> see attached json files , log files (no debug turned on)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
