Hi, I was stress testing the application and found that under heavy use I get a timeout exception from the connection when the NH was lazy loading a relationship.

It is very hard to locate the exact point were this happens, but I've set the command_timeout value to a insanely high value of 1800 (30 minutes) with no success.

Thanks!

Do you mean that some of your tests take more than 30 minutes to complete? :o

Is it an ASP.NET app? IIS may be timing out. Any time you need that long to complete one thing, many other things can mess with you. There could be network issues, garbage collection, virus scanning, etc. causing timeouts.

Do you have log4net configured? What do the logs say? How about the database logs?

For lazy loading, it seems like the command in generated in Loader.cs, in the following method -

protected virtual IDbCommand PrepareQueryCommand(
SqlString sqlString,
QueryParameters parameters,
bool scroll,
ISessionImplementor session )

the command created from

IDbCommand command = session.Batcher.PrepareQueryCommand( sqlString, parameters.CommandType );

doesn't have the correct CommandTimeout set. It is only set if there is a selection.Timeout and I don't see how that is passed.

Is there a way we can set this?