Managed Servers started with no native interface in host controller to connect back to.

When running in domain model if there is a problem starting the native management interface this is not checked and the managed servers continue to be started - the issue with this is that the managed servers can not connect back to their host controller so they end up not really being managed

One issue to keep in mind is that the management interfaces are supposed to start later in the process so that clients can not connect to them prematurely.

Also the following comments already in DomainModelControllerService: -

<bstansberry> darranl: DomainModelControllerService already has this in the block that installs the native mgmt service
<bstansberry> / TODO look into adding some of these services in the handlers, but ON-DEMAND.
<bstansberry> // Then here just add some simple service that demands them

An easy way to reproduce in the past has been to use an incorrectly configured security realm although those issue identified have now been fixed - in the meantime specifying a non-existent security realm should trigger the same failure.