Hi guys,

I have been trying to solve a problem for a client with timeouts on stored procedure calls. We are using LLBLGen (2.6, self servicing) to call stored procedures through

RetrievalProcedures.MyProc()

then using

IDataReader reader = dao.GetAsDataReader

Then using reader.Read(). This all works fine except for I cannot get the timeout to work with anything but the default 30 secs. I have even hard coded

DB.HelperClasses.DbUtils.CommandTimeOut = 120;

And can confirm it is correct in the debugger immediately before the procedure is called but still it times out after 30 seconds. Does the Timeout even work for stored procedures? or is it just for use on views or entities?

Regards,

Rich

Would you please make sure you are using the latest release of v.2.6

It should, but we think it's a bug. We found the same bug in v3 some time ago. We'll port a fix back for you to v2.6. This will be on monday.

It simply works in sqlserver templates, as you can see in DbUtils: check CallActionStoredProcedure and CallRetrievalStoredProcedure.

What database are you using and does it still happen in the latest build? (it's in the templates so you have to re-generate the code with the latest build)

Thanks for the info guys. Dug through the templates and found the problem - I'm using RetrievalProcedures so have to set the timeout for each query like so:

  using (var query = RetrievalProcedures.GetProcMySPCallAsQuery())
  {
                    query.SetCommandTimeout(DB.HelperClasses.DbUtils.CommandTimeOut);
       ...
       ...
   }

Which works a charm.

Thanks,

Rich

Hi, I am having the same problem mentioned in this post, I'm using Self-Servicing, LLBLGen Pro 3.0 to .NET 4.0. I use the following code directly before my stored procedure call, and it does increase the timeout beyond 30 seconds.

DAL.DaoClasses.CommonDaoBase.CommandTimeOut = 45

I think it was mentioned that this is a known bug in v3?

It should, but we think it's a bug. We found the same bug in v3 some time ago. We'll port a fix back for you to v2.6. This will be on monday.

If this is true, where can I find a fix for this bug?

epiazza wrote:

Hi, I am having the same problem mentioned in this post, I'm using Self-Servicing, LLBLGen Pro 3.0 to .NET 4.0. I use the following code directly before my stored procedure call, and it does increase the timeout beyond 30 seconds.

DAL.DaoClasses.CommonDaoBase.CommandTimeOut = 45

So, it won't work if you put that outside the SP method call?

epiazza wrote:

I think it was mentioned that this is a known bug in v3? ... If this is true, where can I find a fix for this bug?

Are you using the latest runtimer library version? (http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=7717)

Note: in the future please don't re-open old threads. Open a new one instead