Smarts: Server logs "Timeout exceeded for block read" message in log file
search cancel

Smarts: Server logs "Timeout exceeded for block read" message in log file

book

Article ID: 303940

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:



 

Smarts application server logs the following message:

[21-Jul-2010 13:49:05+378ms BST] t@114 SM_ProtocolEngine-29 ICS_RSM
CI2-W-CI_BLOCK_READ_TIMEOUT-Timeout exceeded for block read; in file

"/work/bluecurrent/FOUNDATION-7.2.0.X/94/smarts/clsapi/ci_flow.c" at line @ 2733



Environment

VMware Smart Assurance - SMARTS

Resolution

This is normal Smarts server behavior. The Smarts block flow code waits until it receives a block length of bytes (minus 1) before it signals the upstream flow that data is available. It waits until either the deadman timeout or the block timeout expire. In the above problem symptom example, the Smarts server waited till the block timeout expired and logged a warning message. No data loss has occurred at this point.