Timestamps in audit log tables are not ordered

Solution Verified - Updated -

Issue

It seems that timestamps under date column in the various log tables are not always chronological, for example, have the following process:

start->service task 1 -> service task 2 -> end

The entry in NodeInstanceLog table for "EXITING" the "service task 1" looks like this:

7        _2B7478B5-98B3-462F-B5DD-C5E8F1D3E8C3        2016-05-23 10:54:17.539        org.redhat.gss:WrongLogOrder:1.0        _72636572-34E2-474D-A0C6-D23C1BF32E5F        1        Log1         WorkItemNode        WrongLogOrder.WrongLogOrderProcess        1        1        1

The log date is: 10:54:17.539

The entry in NodeInstanceLog table for "ENTERING" the "service task 2" looks like this:

3        _2B7478B5-98B3-462F-B5DD-C5E8F1D3E8C3        2016-05-23 10:54:17.511        org.redhat.gss:WrongLogOrder:1.0        _E1D4E84C-F3F1-48A8-8E8B-EA5028F82DDD        2        Log2         WorkItemNode        WrongLogOrder.WrongLogOrderProcess        1        0        2

The log date is: 10:54:17.511

As you can see - according to the NodeInstanceLog the 'Service Task 2' was entered before the 'Service Task 1' was exited - which doesn't really make sense.

Environment

  • Red Hat JBoss BPM Suite
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.