uml - state machine run-to-completion paradigm -

i did not understand paradigm run-to-completion state machine (14.2.3.9.1 uml 2.5 spec). @ 1 point says:

"run-to-completion means that, in absence of exceptions or asynchronous destruction of context classifier object or statemachine execution, pending event occurrence dispatched after processing of previous occurrence completed , stable state configuration has been reached. is, event occurrence never dispatched while statemachine execution busy processing previous one"

and in another:

"implementation note. run-to-completion mistakenly interpreted implying executing statemachine cannot interrupted, which, of course [of course?? ndr] lead priority inversion issues in time-sensitive systems. however, not case; in given implementation thread executing statemachine step can suspended, allowing higher-priority threads run, and, once allocated processor time again underlying thread scheduler, can safely resume execution , complete event processing"

so, possible or not interrupt state machine?? new high priority event can interrupt current event dispatch?

thanks

mauro

the implementation note refers hard- or software implementation on higher level. completion valid context of state machine. machine may run in global context can allow interrupt processing of state machine. state machine not notice interruption , own view still continues processing. so, mentioned, issue state machines personal watch not run continuously irregular jumps. in normal business processes can neglected, when dealing real-time-processing, might trouble.