Sensor Actiondata has wrong timestamp on Linux systems with AMD processor and using TSC timer

(Doc ID 463731.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3
Linux x86


Running BPEL process with Sensor ActionData on a system with AMD processor and using TSC as
internal kernel timer will cause wrong timestamps in the Sensor ActionData.
Additional this wrong timestamp can cause performance issues during stress tests or in situation with
high workload.

This behaviour can be checked using this small java program :

public class TestCurrentTime {
    public TestCurrentTime() {
        public static void main(String[] args) {
            System.out.println("Checking for monotonically increasing time");
            long from = System.currentTimeMillis();
            for (int i = 0; i < 1000000; i++) {
                long to = System.currentTimeMillis();
                if (to < from)
                System.out.println("Time went backwards");
                from = to;

This program will find out if and how much the time will backward on the OS.

Affected platforms are : SUSE Linux9 and RedHat 4


Do not use TSC timer, configure the kernel to use different timer.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms