Unable to set command_timeout on Update

[vagtborg]

Hi,

I am trying to set the command_timeout but it looks like it only affects Insert actions. Can you confirm if I am using the fluent API correct or if it is not related to fluent API.

A) I set the command_timeout to 10 seconds (just for testing the real value should be higher)
B) I set a trigger on the table to do a wait

1. I do a Insert and that times out after 10 seconds
2. I do a Update and that times out after 30 seconds (default NHibernate value I assume)
3. I tested the same with delete and the timeout is also 30 seconds

Shouldn't the command_timeout affect all commands?

Thanks
Mikkel

Below is the example I used:

I setup a factory like so:

A)

var factory = Fluently.Configure()
    .Database(MsSqlConfiguration.MsSql2008.ConnectionString(conString).ShowSql())  
    .Mappings(m => m.FluentMappings.AddFromAssemblyOf<Program>())
    .ExposeConfiguration(cfg => cfg.SetProperty(NHibernate.Cfg.Environment.CommandTimeout, "10"))
    .BuildSessionFactory();

B)
On my test table I added a trigger (INSERT, UPDATE and DELETE) that just have "WAITFOR DELAY '00:00:45'"

1. When I do a Insert:

using (var session = factory.OpenSession())
{
    using (var transaction = session.BeginTransaction())
    {
        var test = new Testtable() { Time = DateTime.Now };
        session.Save(test);
        transaction.Commit();
    }
}

This times out after 10 seconds.

2. When I do an Update:

using (var session = factory.OpenSession())
{
    using (var transaction = session.BeginTransaction())
    {
        var test = session.Get<Testtable>(1); //Id = 1 is in the DB
        test.Time = DateTime.Now;
        session.Update(test);
        transaction.Commit();
    }
}

This timeout after 30 seconds

[vagtborg]

Hi again,

Sorry to ask again, I was wondering if anyone know about it? maybe I am misunderstanding how to use the API or is this a bug?
I can also try to explain more if needed, would be good to know if I do this wrong or?

Thank you
Mikkel

[Beatles1692]

Have you set the connection timeout too? If connection timeout is less than command timeout obviously it would close the connection before reaching to command timeout.

[krasnyk]

Hi vagtborg,

In my project i have the same problem as you. We are using the NHibernate v4.0 and by:

• update (no matter the timeout values set in the connection string/configuration) the timeout is always 30 seconds
• insert, the timeout value set in the configuration is used (even when the connection timeout in the connection string is set to the lower value as the command timeout)

[asobreiro]

As long as I know, connection time out is the time the system would wait for a connection to "open".. Or wait an available connection from the connection pool (ADO.NET). Command timeout is the (max) time a command would take to execute... These are completely different things.. I didnt knwo it could be different for an update command.

[hazzik]

Transferring to NHibernate as it seems to be NHibernate related.

[hazzik]

This probably is a duplicate of #1158