We might need to use cluster id and network partition id as the key of this map.
Once we are done with this fix shall we do 4.1.3 release build? Thanks On Friday, September 18, 2015, Gayan Gunarathne <gay...@wso2.com> wrote: > When we try to un-deploy the application in a multi region deployment, It > will throw the following exception. > > javax.ws.rs.WebApplicationException: HTTP 404 pods "tomcatr1-pod-1" not > found > > Issue seems like,in a topology service clusterIdClusterMap has only one > value even there is two clusters in two regions. So when un-deploying it is > map to the same region cluster. So when un-deploying the application, first > region will remove successfully but in the second region it will throw the > exception of "HTTP 404 pod not found" > > I think we may need to recheck the logic of adding the clusterIdClusterMap > in the case of multi region deployment. > > Thanks, > Gayan > -- > > Gayan Gunarathne > Technical Lead, WSO2 Inc. (http://wso2.com) > Committer & PMC Member, Apache Stratos > email : gay...@wso2.com <javascript:_e(%7B%7D,'cvml','gay...@wso2.com');> > | mobile : +94 775030545 <%2B94%20766819985> > > > -- Imesh Gunaratne Senior Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
