Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1246139

Summary: [GSS] (6.1.z) JobExecutor: Sorting and paging start behave strange after jobs are created and cancelled
Product: [Retired] JBoss BPMS Platform 6 Reporter: Martin Weiler <mweiler>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: kverlaen, tkobayas, tzimanyi
Target Milestone: CR1   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1210802 Environment:
Last Closed: 2020-03-27 20:03:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1210802    
Bug Blocks: 1249860    

Description Martin Weiler 2015-07-23 14:15:36 UTC 
+++ This bug was initially created as a clone of Bug #1210802 +++

Description of problem:
When lots of jobs are generated and cancelled before executed, paging and sorting starts to behave strange.

Version-Release number of selected component (if applicable):
BPMS 6.1.0.CR2

How reproducible:
After heavy job creation, cancelling and sorting by Id

Steps to Reproduce:
1. Go to Job Perspective
2. Generate several jobs eg. repository cloning and removing. Manually create 15 jobs with dueDate in the future. Go to Scheduled tab and cancel them.
3. Repeat 2. several times.
4. Try to sort by Id jobs in different tabs and use pagination and see the paging work properly for a while and later stop working or is not possible to sort at the same time.

Actual results:
Paging and sorting stops working when lots of jobs are generated.

Expected results:
Paging and sorting works properly.

Additional info:
Improvements to both UI and API to allow server side paging and sorting has been added as part of the work for this feature request:

https://issues.jboss.org/browse/BPMSPL-193

From these changes, the following commits are (partly) relevant to fix the paging problems:

https://github.com/droolsjbpm/jbpm/commit/c085b3b3f5d0da96255380836558be9687d785f2
https://github.com/droolsjbpm/jbpm-console-ng/commit/25c23dcaae69bb78e5a53fd012eaba3a0403e9de
https://github.com/droolsjbpm/droolsjbpm-integration/commit/82f800cc3b662ef2d0a1f6cd780bd4df5dda68db

Note however that backporting these changes won't be a simple cherry-picking...
Comment 8 Maciej Swiderski 2015-08-14 16:31:43 UTC 
backported to 6.2.x branch

droolsjbpm-knowledge
https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/679a532bd9e2ba941c3488834be3324792c062b2
jbpm
https://github.com/droolsjbpm/jbpm/commit/f0e4a3acb6a732d17cbf9deb1c71fb58698ea16b
jbpm-console-bg
https://github.com/droolsjbpm/jbpm-console-ng/commit/173fd614a5226bb7c4ba10f1c15730da0201c1fc

Toshiya,
I left the old methods for queries (without query context) as deprecated and they you underneath once with query context with hardcoded paging information - 0 and 100 meaning it will only return first 100 rows.
Comment 10 Pavel Kralik 2015-09-01 12:01:34 UTC 
BPMS 6.1.3.CR1