Question

Timeout expired, max pool size was reached

Workflow

Updated August 18, 2016

asked on January 8, 2016 • Show version history

Workflow show us this message :

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

After this the workflow ends (Status: terminate)

And this happens not only with querys node, it could happens with find entry or wait entry, invoque workflow, move entry an in different workflows happens the same and its random.

The issue occurs even after a restart of Services (Worflow, Laserfiche, SQL Server).

It´s a Workflow dedicated Server (Server B)

Lasefiche Workflow Versión is : 9.2.1 239
Processor : Intel 2 processors
RAM: 6 GB
OS: 64 Bit - Windows Server 2012 R2

SQL and LF Server (Server A)

There it´s not any runaway workflows (out of control)

We generate a trace from SQL Profiler and found deadlocks

We do a DB maintenance Including the following Check, Fragmentation and Update of statistics, all this with the Laserfiche services down and after this the error persist.

0 0

Replies

replied on January 8, 2016

There isn't enough information to troubleshoot. Was SQL overloaded at the time this happened? How many connections were to SQL when this happened? What were the deadlocks you found and were they from Workflow queries?

0 0

replied on January 12, 2016

The server where SQL it´s installed also Laserfiche it´s installed too in the same server.
The RAM was about 90% and CPU 24 - 50%

When this happen we have about 160 coneections to the same bd Workflow application Data base.

The deadlocks we found where in the sql Trace , not exactly in workflow queries can happen in find entry node or move entry node we note that when we see the workflow history and it´s termited and show the following error : "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached." .

0 0

replied on August 18, 2016

Hi David

Do you solve this issue? If you did, how you do it?

Thanks and regards

0 0

replied on August 18, 2016

Hi Ricardo.

we apply an index provided by Laserfiche with the following:

CREATE NONCLUSTERED INDEX wait_condition_wf_ix ON wait_condition
(
instance_id,
workflow_id
)

on workflow DB and that solve the issue for a little bit of time.

Then the issue came again and we decide to export al exercises and create a new Workflow data base with that index. And the error is not present right now.

0 0

You are not allowed to follow up in this post.

Question

Question

Timeout expired, max pool size was reached

Replies

Sign in to reply to this post.