On the Windows platform, the mqfailover command requires pressing Control+C keys to exit the hung process. You must rerun the setup-one-machine-cluster process.
From install_dir\samples\ee-samples\failover\apps\mqfailover\docs\index.html, run the following commands:
Console 1
cd install_dir\samples\ee-samples asant start-mq-master-broker1 |
Console 2
cd install_dir\samples\ee-samples asant start-mq-cluster-broker1 |
Console 3
cd install_dir\samples\ee-samples asant start-mq-cluster-broker2 |
Console 4
cd install_dir\samples\ee-samples asadmin start-domain domain1 |
If you have already executed asant setup-one-machine-cluster-without-ha or asant setup-one-machine-cluster-with-ha for any other Enterprise Edition sample, execute asant configure-mq. Otherwise, execute asant setup-one-machine-cluster-and-configure-mq. In this case, the command appears to succeed:
start_nodeagent: [echo] Start the node agent cluster1-nodeagent [exec] Command start-node-agent executed successfully. |
But then the system hangs indefinitely.
None. This problem similarly affects all Enterprise Edition samples that use this ant target on Windows. A workaround is to press Control+C to exit the hung process and then rerun it.