[IBATISNET-151] Pre-load stored procedure parameters should use the already-open connection of the IDalSession

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: DataMapper 1.3
• Fix Version/s: DataMapper 1.5
• Component/s: DataMapper
• Assignee: Gilles Bayon
• Reporter: Gilles Bayon
• Due: 30/Mar/06
• Created: 31/Mar/06 01:32
• Updated: 08/Apr/06 19:39
• Resolved: 08/Apr/06 19:39

Description

Report by
Chris Bissell
Managing Architect
MySpace.com

The only performance optimization we've made so far is to ensure that the
call to pre-load stored procedure parameters borrows the already-open
connection of the IDalSession above it. We saw that under super-heavy load
the fact that the sproc parameter populator tried to grab its own connection
within the connection of its parent that a semi-deadlock situation would
result, because the parameter populator does all its work in a heavy lock.
Interested in hearing why this was done, because we definitely got a big
boost on app startup post-optimization.