In previous versions of DAnCE it was possible to 'alias' nodes by creating a node manger map that provided the same corbaloc IOR to more than one node name.  This is no longer supported.  

The crux of the issue is that the NodeManager implementation stores the NAM instance in a map associated with the subplan UUID that is provided by the preparePlan operation, so when the second invocation to preparePlan arrives with a plan containing an identical UUID, it sees that a NAM already exists and bails.  

I think this method of storing the NAM is a good thing, so I see two ways to address this issue:

1.  Construct subplan specific UUIDs by appending the name of the node to the name of the original plan.  This makes some sense to me on a conceptual level, as the node-specific subplans are no longer *the entire plan* and thus them having the same UUID doesn't make quite so much sense.  On the other hand, from an administrative point of view, this might complicate future re-planning and re-deployment capability. 

2.  Add support for launching more than one  NodeManager instance with a process.   The startup mechanism is designed to eventually support this capability.  This would probably provide the most predictable behavior, as it would provide an environment most similar to if the aliased nodes were in fact separate nodes - but would require that additional command line arguments be provided by the user when launching the NodeManager process. 

James, any comments are welcome.