search

mbrimble / biztalkdocumenter

Microsoft Public License
13 stars 9 forks source link

BizTalk Documenter 2013 R2 - Timeout expired error. #13

Open supriyakaragave opened 6 years ago

supriyakaragave commented 6 years ago

Hello, we are getting below error when trying to generate a Document for one of our application. Rest of the other applications are able to generate the output just fine. If anyone has faced the problem and knows the solution, it is greatly appreciated. Thanks in advance. _--------------------------- Error Generating Documentation

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.

OK
---------------------------_

pvandenheede commented 6 years ago

Have you tried limiting the number of applications/orchestrations? Sometimes it's necessary to document it multiple files I have found.

supriyakaragave commented 6 years ago

Hello, I have multiple Applications deployed on BizTalk server. This error occurs only in one of the Application. I have tried to generate the documenter CHMs individually for Integrations in this particular application.

I tried to modify the source code to troubleshoot but there is a DLL version dependency error.

jankena commented 5 years ago

Hello, the same happens to us when creating documentation for one of our BizTalk applications. It is the only one that causes the problem. It seems that Documenter encounters and issue with some of the artifacts in the application that causes it to leak SQL connections and exhausts connection pool. It remains exhausted until restarting the Documenter.

Dijkgraaf commented 5 years ago

@jankena Could you isolate which artifacts that caused the errors?

supriyakaragave commented 5 years ago

@Dijkgraaf .. I debugged the source code and located the root cause. This happened when schema was very complex, including multiple Imports too. The code piece where all Schemas and Maps (we were using XSLT mapping) are read from SQL and converted to XML before being documented causes the TimeOut error. I changed the code to exclude Schemas and Maps for that particular Application. With this change I was able to document other artifacts at least. Hope this helps you with fix. I was in little rush to wrap it up so did not try to debug and fix the problem itself.