[KULRICE-9045] ViewServiceImpl - buildView - DB Connections Created: 27/Feb/13  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development, User Experience (UX)
Affects Version/s: 2.2
Fix Version/s: Backlog
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Jeff Domeyer (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is related to KULRICE-6557 Improve Performance and Memory Consum... Closed
Similar issues:
KULRICE-6719Add LOG level checks to logging in ViewServiceImpl buildView and getViewById
KULRICE-6757KSPD: Investigate Optimization options for ViewServiceImpl
KULRICE-5102Add table connecting Context and Rule in DB, and update the model to reflect this relationship
KULRICE-13560Install XA Connection Pool fix on env17 and re-run concurrent user tests
KULRICE-12941Install XA Connection Pool fix on env17 and re-run concurrent user tests
KULRICE-4672create piece to connect rules into actions
KULRICE-10973KD 2013 Install Fest Prep: Zip up Maven repository and Rice db source code
KULRICE-10970KD 2013 Install Fest Prep: Create Rice DB SQL script
KULRICE-12918XA Connection Pool Does Not Wait For Connection
KULRICE-10221KRAD Component Suggest doesn't return results from db table
Epic Link: Performance
Rice Module:
KRAD Feature Area:
KAI Review Status: Not Required
KTI Review Status: Not Required
Include in Release Notes?:


At the moment, buildView in ViewServiceImpl is ultimately going to call authorization checks for things like can you edit/route/save etc... a document. Each of these calls will open a new transaction/connection as the first time a transactional boundary is reached is down in the businessObjectService/DAO.

I took the easy route and just placed a transactional annotation on buildView and that cuts down on the connections opened from >30 down to about 5 per view build.

Generated at Tue Jul 07 08:20:32 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.