Here is a sample message of the database connection recovery. After receiving the Communication failure message, Process Engine will automatically recover the terminated database connection, retry the transaction, and continue to function. Please keep in mind that even with the messages in the elogs, this error does not impact Process Engine with respect to data integrity or affect usability. The Microsoft SQL 7886 error does not occur with READ_COMMITED isolation level. This error can occur for Process Engine when the following conditions are met:ġ) The BLOB objects associated with workflow work objects are large (90K+)Ģ) There is reasonable load on the Process Engine server, where the VWKs processes are all processingģ) The work objects are all being processed from the same database table in the databaseĪccording to Microsoft, the way to remove or eliminate the errors is to not use the READ_UNCOMMITTED isolation level. When Microsoft SQL Server returns this error to the client application, it will also terminate the connection. Now at the same time User B fires a query with NO LOCK hint to access that row, It finds the pointer that redirects it to the actual data page but when it reaches there it doesn’t find the data because it has been deleted So it might return this error message. For example, User A has fired a query to delete a row and the query finds a pointer that points to a location where actual data is lying and it deletes that data. Read failure on LOBs, probably due to read uncommitted isolation level, or nolock scans. Microsoft provided the following explanation of the 7886 error, and a condition when this error may be returned by SQL Server: By default, the IS database libraries, when communicating with Microsoft SQL, uses READ UNCOMMITTED isolation level for transactions. Process Engine 4.5.1 relies on the Image Services (IS) 4.1.2 database libraries to communicate with and execute transactions in the database. This can occur on Microsoft SQL Server 2003 or 2008. A common cause for this is if the application is running in READ UNCOMMITTED isolation level.
Microsoft SQL Server will log a corresponding entry in the SQL Server error logĪ read operation on a large object failed while sending data to the client. Įrror in GDBY_logoff: SQLEndTran DBC, hdbc=13038296 (&01d3e0d0), COMMIT (.\src\GDBY.c, VERSION 4.1.1.1, = 08S01, NativeError = 0,ĮrrorMsg = 'Communication link failure' The following errors are logged in the Process Engine 4.5.1.x elog or in the Windows application event log:ĥ 10:06:38.476 121,0,41 VW/Process (1288.7084.64 0x508.1bac).
0 kommentar(er)
