Description of problem: Platform BZ for https://issues.jboss.org/browse/JBPM-3813 How reproducible: Cannot reprocude on my side. But a customer can reproduce it constantly. Non-reproducible issue may not be accepted but we can guess the root cause and the fix is reasonable. Steps to Reproduce: 1. Create a process with some Script task nodes and one Human task node. (See attached repository_export_multi_marker_issue.zip) 2. Start a process with jBPM Console 3. Click 'Diagram' button Actual results: The diaglam has multiple markers. (See attached testprocess.png from the customer) Expected results: The diaglam has one marker on a Human task node.
Created attachment 619726 [details] repository_export_multiplemarkers.zip
Created attachment 619728 [details] testprocess.png
Maciej Swiderski <swiderski.maciej> made a comment on jira JBPM-3813 As mentioned in pull request, changing order of the query to provide first all enter events and then exit events could cause some issues if someone that uses this method relies on enter-exit pairs (even though this issue is about that not every time such order is delivered). I see two alternative options: 1. change order of the queries to be "date, id" where id is identifier from sequence so exit event should never have smaller value than enter for the same node instance 2. implement sorting mechanism in GraphViewerPluginImpl.getActiveNodeInfo() to sort it first enter events and then exit events and keep the logic of that method unchanged Wdyt?
Toshiya Kobayashi <tkobayas> made a comment on jira JBPM-3813 Thanks Maciej, Yeah, you are right. I think option 1 is better because it would prevent future issues like this.
Maciej Swiderski <swiderski.maciej> made a comment on jira JBPM-3813 Toshiya, is it ok to close pull request for this? I'll make changes and push it into master as agreed. Thanks
Toshiya Kobayashi <tkobayas> made a comment on jira JBPM-3813 Sure, thanks.
Maciej Swiderski <swiderski.maciej> updated the status of jira JBPM-3813 to Resolved
Maciej Swiderski <swiderski.maciej> made a comment on jira JBPM-3813 implemented option 1 (added id into order by) and merged into master and 5.4.x
*** Bug 806896 has been marked as a duplicate of this bug. ***
merged into 5.2.x
I haven't seen this issue in ER4 in any of the tests run. This issue is either fixed or so well hidden that it can be considered non-existent.
We have downloaded and installed BRMS 5.3.1 on Oracle Database 11g, however we still see two wrong markers when we display process instance map. Given that we downloaded the latest jbpm-bam-5.3.1.BRMS.jar which contains the correct ordering in JPAProcessInstanceDbLog.findNodeInstances(). On the other hand we tried rebuilding the guvnor packages again but didn't work as well.