Running four nodes in single server is not recommended at integration tests phase, so killing a worker node at integration tests run time is not possible (Even no admin services exposed in worker nodes to forcefully shutdown the instance) I'm not sure whether upcoming operation center will facilitate this kind of functionality.
Proposed deployment framework can be used to achieve this. However work is still under progress. You can find the relevant readmine at [1] Please find relevant mail discussions on worker node management in automated tests at [2] [1] https://redmine.wso2.com/issues/2083 [2] http://mail.wso2.org/mailarchive/dev/2013-November/024977.html Thanks, Krishantha On Fri, Oct 24, 2014 at 6:21 PM, Pubudu Dissanayake <pubu...@wso2.com> wrote: > Hi Folks, > > I've implemented Hazelcast based Tomcat Session Replication feature for > Appserver [1 <https://redmine.wso2.com/issues/2816>].I have few concerns > over integration tests for this feature. > > Following is the basic cluster scenario that I have to be written as > integration tests. > Environment : *WSO2 ELB, 1-Mgt+2-Worker (WSO2 AS) * > > Basic scenario ( Assume 'x' webapp deployed in Mgt node and enabled > dep-sync with two worker nodes. ) > > Say that we have above mentioned setup. Since our ELB is session aware, it > will send the requests to the same node based on the seesionID. And when > that node goes off line, it will route the requests to the other node. But > if we have enabled replication, this routing should work seamlessly where > the session, which was replicated and will be used by the second node. > > - Start Mgt and WorkerNode-1 --> Change session values at WorkerNode-1 > --> Start the WorkerNode-2 --> Perform kill -9 operation on WorkerNode-1 > after Workernode-2 complete it's start up operation. Then check whether > those session values changes are reflected at WorkerNode-2. > > > - After Change session values at WorkerNode-2 while WorkerNode-1 off > line --> Start the WorkerNode-1 --> Perform kill -9 operation on > WorkerNode-2 after Workernode-1 complete it's start up operation. Then > check whether those session values changes are reflected at WorkerNode-1. > > This routing should work seamlessly where session attributes are > replicated among all nodes. > > Basically I have to write an integration test to evaluate the feature. > Please guide me through the process how should I carried out and any > references to help me further to achieve this integration test? Let me know > if you need any further suggestions. > > - Pubudu > > [1] https://redmine.wso2.com/issues/2816 > > > -- > *Pubudu Dissanayake* > Software Engineer > > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > Mob: + 94 775 503 304 > > Blog: http://geekdetected.wordpress.com/ > Linkedin: *http://lk.linkedin.com/in/pubududissanayake* > <http://lk.linkedin.com/in/pubududissanayake> > Flickr : https://www.flickr.com/photos/pubudufx/ > Twitter: https://twitter.com/GeekInAction > > -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear.
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
