WDT not creating optional MBeans in the domain config.xml

[TheFrogPad]

A WDT model file specifying an empty ServerFailureTrigger does not result in the MBean being present after using the domain creation tool.

Workaround: Specify one of the ServerFailureTrigger settings, then the MBean will be present in the resulting config.xml. For example:

topology:
    Server:
        ManagedServer2:
            ListenPort: 7005
            OverloadProtection:
                ServerFailureTrigger:
                    MaxStuckThreadTime: 600
     

WebLogic has certain optional MBeans like ServerFailureTrigger and JTAMigratableTarget where the existence of the MBean causes WebLogic to behave differently.

A WDT model file that specifies such an optional MBean without providing any settings should still result in that MBean being present in the domain config.xml file.