Hi Alvaro,
This issue came up with another customer and this is the reply I sent after identifying that the problem was a result of calls made to the baseline DotNetNuke API for managing images.
Our calls to create the images are run through the DNN APIs, which we
have checked to make sure connections are handled properly. It may just
be that between the db activity required by DNN and the added db
activity needed to write the file related information for each new image
to the database, we simply exceed the default connection pool size set
by your hosting provider. Others who have run into this same issue have
addressed the issue by adding the following to their connection string
in the web.config: pooling=true;Max Pool Size=50;" /> At this point,
this issue seems to be isolated to certain environments and certain
providers, and the workaround above seems to address the issue. If you
are working with posts that contain large numbers of images, the Max
Pool Size value may need to be increased. Please let us know if this
doesn't address your issue.
Thanks and be sure to let us know if you need help implementing this workaround or if it doesn't solve your problem.
Don