This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
"A Timeout Expired" error occurs in K2 Workspace when more than 200 instances are started simultaneously. The cause of this error is that the SmartBroker database connection pool is not re-used and starts running into timeouts.
|Note: The steps below describe one scenario under which these errors may occur. These steps are simplified and not all steps are shown or described.|
Run a custom console application with commandline arguments of: [HostServerName] [Number of Instances to start]
Use this SQL query to determine the number of connections:
SELECT spid, kpid, status, loginame, hostname, blocked, db_name(dbid), cmd FROM master..sysprocesses WHERE db_name(dbid) = 'SmartBroker'
The following error message relates to this issue:
- "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached."
This Hotfix is contained within the latest K2 blackpearl 0807 Update. Install the update package to resolve the error.
The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx