jBPM project issue related to SOA-1507/JBESB-2846 (bpm_orchestration2 process is not safe)

The jBPM logging is currently handled through Token.addLog and, regardless of whether the log object is persisted or not, results in the modification of the associated token.

This happens because the ProcessLog.setToken method invokes the Token.nextLogIndex method, causing a change in the token and, therefore, a potential conflict with any other tokens in the process.