Pre-load stored procedure parameters should use the already-open connection of
the IDalSession
----------------------------------------------------------------------------------------------
Key: IBATISNET-151
URL: http://issues.apache.org/jira/browse/IBATISNET-151
Project: iBatis for .NET
Type: Bug
Components: DataMapper
Versions: DataMapper 1.3
Reporter: Gilles Bayon
Fix For: DataMapper 1.3
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
