vmcj/max_inline_sleeps is a SAP Parameter attribute which is used to control Max. number of inline sleeps during VMC processing information. This is available within R/3 SAP systems depending on the version and release level.
Below is the standard documentation available and a few details of the attributes values .
When a VMC request is executed, a VM can (in rare cases) encounter a situation where it needs to wait for an external event. Examples of this are waiting for a shared garbage collection or releasing VMs when internal sessions are deconstructed. Since no roll-outs are usually possible here, the VM is deactivated for a brief period. A drawback of this is that the work process in question is occupied for this period. To avoid deadlocks in extreme situations, this deactivation can be limited. There are two different situations: a) Deactivation during the roll-out b) Any other deactivations a) The Java session is saved during the VMC roll-out using a callback to the Java VM. In rare cases, this is not immediately possible (for example, when a memory bottleneck causes a wait for the end of a shared garbage collection). Within the VMC, the VM in question is deactivated for a short period (known as a sleep). To prevent the roll-out from being delayed too often, a maximum number of delays can be defined here. Once this is reached, the VM moves to the state "PRIVATE" and processing is resumed when the next request is edited. b) All other delays can also be limited. The request must be canceled once this number is reached. The parameter values must be specified using the following syntax: vmcj/max_inline_sleeps = [ROLL_OUT=<(><<)>number1> , ] [NORMAL=<(> <<)>number2> ]
vmcj/max_inline_sleeps = NORMAL=60, ROLL_OUT=10 If the value -1 is specified, the number of delays is unlimited.
See SAP Parameter Documentation for full SAP documentation for this profile parameter.