Bug 1022587
Summary: | BPEL History requests time out with production-level historical data in db | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Rick Wagner <rwagner> | |
Component: | riftsaw | Assignee: | Nobody <nobody> | |
Status: | VERIFIED --- | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 5.3.1 | CC: | nwallace, ppecka, rwagner, soa-p-jira | |
Target Milestone: | GA | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1024013 (view as bug list) | Environment: | ||
Last Closed: | 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: | ||||
Bug Blocks: | 1073034 |
Description
Rick Wagner
2013-10-23 15:15:27 UTC
Although the query has been simplified a bit, the nature of the information being retrieved makes it difficult to do a simple optimised query. Therefore the main solution to this problem has been to introduce pagination in the BPEL console to reduce the number of process instances retrieved for each request. The fix is available in the following component/versions: http://anonsvn.jboss.org/repos/riftsaw/tags/RiftSaw-2.3.9.Final/ http://anonsvn.jboss.org/repos/riftsaw/tags/RiftSaw-ODE-2.3.9.Final/ https://github.com/bpmc/bpaf-explorer/releases/tag/1.0.2.Final https://github.com/bpmc/bpm-console/releases/tag/2.2.12.Final This BZ was thought to be included in Roll up SOA-P_5.3.1_4_2013, but it was not. Bumping to SOA-P_5.3.1_1_2014. Hi Rick, I'm unclear what the problem is, as 1024013 (which is essentially the same issue but for FSW6) has been QA'ed and marked verified. Are you sure the fix was included in the version you tested? i.e. was the pagination present in the BPEL console? If so, do you have the SQL debug info to indicate how many queries it was attempting to run as described in step 2 of the original problem description? (In reply to Gary Brown from comment #3) Hi Gary, Thanks for the quick response. This fix was supposed to have been included in the previous 5.3.1 Roll up, but we've been informed it didn't make it. (The FSW fix is orthogonal to this.) So I think the answer to your question about inclusion is 'No, we made a mistake and did not include it'. I think we just need to make sure the code you cited in comment #1 above is included in this next 5.3.1 Roll up. No new code is requested this time around. Thanks, Rick Ah ok - thanks for the clarification Rick. As the verified status had been set to FailedQA I thought possibly there was a problem with the fix :) Should I set the status to modified? Or will someone else do that when the next roll-up is being built? Hi Gary, I got it. Thanks for checking up. Rick (In reply to Gary Brown from comment #5) > Ah ok - thanks for the clarification Rick. > > As the verified status had been set to FailedQA I thought possibly there was > a problem with the fix :) > > Should I set the status to modified? Or will someone else do that when the > next roll-up is being built? |