2221539 - Mutex initialization failed in step runBootstrap

During the installation of a Java Application Server instance the step runBootstrap fails. 
SAPinst logs display the following error:

ERROR 2015-05-11 12:53:54.390 (root/sapinst) [CSiStepExecute.cpp:1187] id=controller.stepExecuted errno=FCO-00011
The step runBootstrap with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|di|0|runBootstrap was executed with status ERROR ( Last error reported by the step: Process call '/usr/sap/<SID>/J<nn>/exe/jstart pf=/usr/sap/<SID>/SYS/profile/<SID>_J<nn>_<hostname> -file=/usr/sap/<SID>/J<nn>/exe/startup.properties -nodename=bootstrap -launch' exits with error code 1. For details see log file(s) jstart_bootstrap_J<nn>.log.).

Where <SID> is the SAP System SID and <nn> is the number of the new instance being installed.
The detailed log pointed in the error message (jstart_bootstrap_J<nn>.log) may be empty. In such cases refer to the dev_bootstrap file instead, which is available in the same location.

The dev_bootstrap file shows the following additional details:

 ********************************************************************************
 *** ERROR => Mutex initialization failed.
 ***
 *** Please see section 'Launcher initialization issues'
 *** in SAP Note 1316652 for additional information and trouble shooting advice.
 ********************************************************************************

*** LOG => exiting (exitcode 556, retcode 1).

Checking the jvm_bootstrap.out file located in the work directory of the affected instance (/usr/sap/<SID>/J<nn>/work) the following or similar messages are also present:

Starting to synchronize native files
Thread [Watchdog for main] initiated a full thread dump on [Thu May 11 18:56:52 EDT 2015] due to: [Watchdog timeout]
Exception occurred for component [internal/unkown] of type [unkown]
com.sap.engine.bootstrap.SynchronizationException: No progress was recorded since [ Thu May 11 18:55:23 EDT 2015]. Check the database and file system state. If you are using MAXDB ensure that the log and data volumes are not full
at com.sap.engine.bootstrap.Bootstrap.timeout(Bootstrap.java:343)
at com.sap.engine.lib.time.Watchdog.run(Watchdog.java:95)

• Relevant to Java based instances only
• Any SAP Netweaver Release
• Software Provisioning Manager tool release independent

SWPM, additional application server, dialog instance, kernel, work traces, TroubleTicket, java.log, sapinst_dev.log, properties, timeout, sapinst, system copy, stack split , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-INS-JCI , Java component inst. / jload jmigmon, jsizecheck , Problem