On Mon, Nov 3, 2014 at 11:05 AM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
If that's the case, we can go ahead with graceful server shutdown restart
approach.
+1 for the approach
Also write some integration test cases using HZ Map EntryListener as-well.
With this, you can
If that's the case, we can go ahead with graceful server shutdown restart
approach.
Also write some integration test cases using HZ Map EntryListener as-well.
With this, you can test what was the exact values updated for the session
replication scenario from different nodes.
On Sat, Nov 1, 2014
Thanks for the reply, I'll update our redmine [1] accordingly
On Mon, Oct 27, 2014 at 7:33 AM, Krishantha Samaraweera krishan...@wso2.com
wrote:
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
Hi All,
In WSO2 Operations Center we are currently supporting only
forceful/graceful restart/shutdown. To do this, we use the ServerAdmin
service. This is similar to restarting/shutting down the server with
management console.
If you want to restart/shutdown a server you can use the ServerAdmin
On Fri, Oct 31, 2014 at 6:47 PM, Pubudu Dissanayake pubu...@wso2.com
wrote:
Thanks for the reply, I'll update our redmine [1] accordingly
On Mon, Oct 27, 2014 at 7:33 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Running four nodes in single server is not recommended at
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
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 :
