<p>Indicates whether insertion is paused at startup on destinations
targeted to this JMS server. A destination cannot receive any new
messages while it is paused.</p>
<p>When the value is set to <code>true</code>, then immediately after the host
server instance is booted, then this JMS server and its
targeted destinations are modified such that they are in a "insertion paused"
state, which results preventing messages that are result of
the "in-flight" work completion to arrive on those destinations.</p>
<p><b>Note:</b> For a detailed definition of "in-flight" work/messages, see
weblogic.management.runtime.JMSServerRuntimeMBean#resumeInsertion
and
weblogic.management.runtime.JMSDestinationRuntime#resumeInsertion</p>
<p>To allow in-flight work messages to appear on the destinations,
later you will have to change the state of this JMS server to an
"insertion enabled" state by setting this value to <code>false</code>,
and then either redeploy the JMS server or reboot the hosting server instance.</p>
<p>When the value is set to <code>default</code>, then the Insertion Paused At Startup
is determined based on the corresponding setting on the individual destination.</p>
(Interface=weblogic.management.configuration.JMSServerMBean Attribute=getInsertionPausedAtStartup)