As you say below, the node surviving node continues to work fine when I "kill -9" the other. My problem is that when I do a "graceful" shutdown of the node that contains the "MasterConfigurationStore". When I do this it not only shuts down the node and obviously that node's application, but it also shuts down the application on the surviving node. This is a problem.

hi,
WADI is targeted for exceptional case such as
"ctl-c" , "kill -9" shutdown web container, if you directly shutdown server, it won't replicate session.
You can refer to section "What are WADI's goals?" of wadi page: http://wadi.codehaus.org/faq.html#status, for your convenience, i pasted it here:What are WADI's goals? [08/06/04]

In the Web tier, we can crystallise WADI's goals into two stages:

To be able to walk into your web farm and 'ctl-c' any webcontainer node without losing any HttpSessions (i.e. customers).

To be able to walk into the same web farm and 'kill -9' any webcontainer node without losing any HttpSessions (i.e. customers).

The first of these two cases is important because it allows easy maintenance of existing h/w or s/w. This may seem a trivial requirement, but many existing solutions are time-consuming and/or error-prone (involving draining sessions off target nodes over long periods etc.), to the point that many sites simply accept that maintenance will impact quality of service. The second of these two cases deals with a more exceptional case - the catastrophic failure of a webcontainer node. As online competition for business increases, systems are being required to provide higher and higher levels of availibility. This can be critical in particular areas. The ability to preserve web-tier state beyond the failure of its node is correspondingly an increasing requirement.

I have two installations of Geronimo 2.1.5 installed on the same test server.
Each installation has multiple instances. Â Iâ€™ve created a cluster using
installation1, instance1 (nodeA) and installation2, instance2 (nodeB). Â The
logs indicate that each node is a cluster member.

To help with application management, Iâ€™ve created a Farm with nodeA and
nodeB as the only members. The test application was successfully deployed to
the MasterConfigurationStore and is available on both nodes. Â Also, stopping
the application using G_MASTER will stop the application on both nodes. Â So
far, so good. Â All seems to be working fine.

The problem comes when I do a graceful shutdown of the Geronimo instance
which I used to deploy the application to the MasterConfigurationStore
(nodeA). Shutting down this instance also causes the application on nodeB to
stop. Not so if I â€œkill -9â€ the specific instance process.
Is this the expected reaction to a graceful shutdown?

Also, I tried configuring the default instance of installation1 as a member
of the Farm and than deploying the app to it (rmi=1099). Â The app deploys
okay to the clustered instances but the app on installation1, instance1
(nodeA) will not start and stop through the Farm. Â Any suggestions?