[Top] [All Lists]

Re: Timeout expired Procedure: ConnectionRead (recv()).

Subject: Re: Timeout expired Procedure: ConnectionRead (recv()).
From: Joe Webb
Date: Wed, 22 Jun 2005 06:17:04 -0500
Newsgroups: microsoft.public.sqlserver.notificationsvcs
Hi - 

My understanding of your post is that the rule that generates the
notifications over large batches is timing out. Right? 

Some thoughts to consider:

Do you have any indexes (defined using T-SQL statements in the ADF)
for the subscription and events tables? If not, that's probably where
I'd start. Creating an index on the base tables will help improve the
performance of the dynamically created views.

Are the rules joining any linked servers? If so, that sometimes
creates less than optimal performance.

You can also adjust the ActionTimeout element in the rule declaration,
but the default 30 minutes is typically enough. I'd look for
optimization techniques first. 


Joe Webb
SQL Server MVP

Get up to speed quickly with SQLNS 

I support PASS, the Professional Association for SQL Server.

On Mon, 20 Jun 2005 18:38:59 -0400, "InvalidLastName"
<[email protected]> wrote:

>From time to time, where there was large event batch, which may contain over
>10,000 events, the SQL-NS failed to generate the notifications, and the
>following error was logged in the event log:
> <Description>
>  The view of the event class could not be materialized.
> </Description>
> <Context>
> <InstanceName>SQLNSDemoInstance</InstanceName>
> <ApplicationName>SQLNS</ApplicationName>
> <EventClassName>SQLNSDemoEvents</EventClassName>
> <QuantumId>14451</QuantumId>
> <EventThrottle>500000</EventThrottle>
> Source: .Net SqlClient Data Provider
> Number: -2
> State: 0
> Class: 10
> Server: (our database sever)
> Message: Timeout expired.  The timeout period elapsed prior to completion
>of the operation or the server is not responding.
> Procedure: ConnectionRead (recv()).
> Line Number: 0
> </Context>
> <Description>
>  Timeout expired.  The timeout period elapsed prior to completion of the
>operation or the server is not responding.
> </Description>
> <Instance>SQLNSDemoInstance</Instance>
> <ApplicationName>SQLNS</ApplicationName>
> <Component>Generator</Component>
> <Thread>146</Thread>
>For more information, see Help and Support Center at
>Here are some search results from google
> ( this is related to distributor,
>but our case is on generator instead)
>However, in our case when the error was logged, the database is still
>accessible. It doesn't look like the database server is under extreme heavy
>load at the time.
>Is there a way to identify what really caused the issue ? (Is this ADO
>command timeout or connection out?) Any resolution for this ? (change ADF or
>SQLNS .config file)
>Also, when such error occurred, how can we re-generate these notifications ?

<Prev in Thread] Current Thread [Next in Thread>