[
https://issues.apache.org/jira/browse/STRATOS-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020435#comment-15020435
]
ASF GitHub Bot commented on STRATOS-1628:
-----------------------------------------
GitHub user R-Rajkumar opened a pull request:
https://github.com/apache/stratos/pull/492
implementing STRATOS-1628
Currently, integrations test is looking at specific log messages to
determine whether the stratos server is ready to handle request or not. Proper
way would be to check with an API whether the server is ready or not. This PR
is to implement this check in the following way.
a) exposing an API in mock API to check whether mock iaas is activated or
not.
b) integration tests should be started after getting a positive response
from the above API.
As per our component start up order, the above solution will make sure that
every component is ready to handle requests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/R-Rajkumar/stratos stratos-4.1.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/stratos/pull/492.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #492
----
commit 710485771d4a7a89c79d180cea5fa9c780d86a3c
Author: rajkumar <rraju1...@gmail.com>
Date: 2015-11-21T12:34:11Z
implementing STRATOS-1628
----
> Improve the way intergration test determines whether the server is ready or
> not
> -------------------------------------------------------------------------------
>
> Key: STRATOS-1628
> URL: https://issues.apache.org/jira/browse/STRATOS-1628
> Project: Stratos
> Issue Type: Improvement
> Components: Integration Framework, Mock IaaS
> Reporter: Rajkumar Rajaratnam
> Assignee: Rajkumar Rajaratnam
>
> Currently, integrations test is looking at specific log messages to determine
> whether the stratos server is ready to handle request or not. Proper way
> would be to check with an API whether the server is ready or not. I propose
> we need to handle this in the following way.
> a) exposing an API in mock API to check whether mock iaas is activated or not.
> b) integration tests should be started after getting a positive response from
> the above API.
> As per our component start up order, the above solution will make sure that
> every component is ready to handle requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
