I got Lasitha's web apps and tried to recreate the issue. In his scenario, he's deactivating the service from the UI. Once the service is deactivated, when you send a request to that endpoint, it redirects you to the Carbon login page with a HTTP 200 OK.
Response headers: HTTP/1.1 200 OK Set-Cookie: JSESSIONID=BF80113B54C712FAA4810A027BA1CB03; Path=/; Secure; HttpOnly X-FRAME-OPTIONS: DENY Content-Type: text/html;charset=UTF-8 Content-Language: en-US Transfer-Encoding: chunked Vary: Accept-Encoding Date: Wed, 08 Jul 2015 12:18:01 GMT Server: WSO2 Carbon Server So it actually does not consider it as a failed scenario. That is why it's not failing over. @Lasith, could you kindly try with an actual scenario where the endpoint fails? Regards, Evanthika On Wed, Jul 8, 2015 at 2:03 PM, Lasitha Deergawansa <[email protected]> wrote: > Hi All, > > I'm in process of automating Failover end point function test case - > APIM-45 [1] and figured out the Failover Endpoint function is not working > in APIM 1.9.0. This is a blocker for the completion of the test case. > Tracking purpose I have created a JIRA APIMANAGER-3967 [2] > > Steps to recreate: > 1. Create, Publish and Subscribe a API with "Endpoint Type=Failover > Endpoint" with a production endpoint and multiple production failover > endpoints. > 2. Send a request to the API and it will correctly invoked the production > end point. > 3. Make the production end point unavailable and send the request again > 4. No response from the API. > > > > > [1] > https://testlink.wso2.com/linkto.php?tprojectPrefix=APIM&item=testcase&id=APIM-45 > [2] https://wso2.org/jira/browse/APIMANAGER-3967 > > > > Thanks & Best Regards, > Lasitha. >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
