Forum Discussion
Error RSPortal: obtaining a connection from the pool
I've worked on this issue with the support. Issue number is 121020321001710.
There is a demo dashboard with Adventure Works Tabular Model and some slicers and filters.
We've fixed the issue by increasing
<MaxCatalogConnectionPoolSizePerProcess> to 500.
This is likely NOT a desktop specific issue. The reason you see the change when saving with a specific version of desktop is likely just the state of the "enhanced model metadata" feature. There is likely an issue with cleaning up unused connections in PBIRS itself. Working with server team to try to reproduce this issue now, but we were running into some trouble getting it to break. Have you seen this issue on a simple report with slicers or has it been on more complicated reports with many visuals + slicers?
For now you can increase the number of connections in the config file as one use suggested, or use reports with enhanced metadata disabled. I will update you when we know more.
Petebro I reproduced the issue as following:
- Create new Power BI report with live connection to tabular model.
- Added 4 visual with existing measures and different dimensions.
- publish it to PBIRS.
- Restart PBIRS to see zero RS Portal connection.
- Start to drilldown/filter visuals and apply filters via filter sections.
- I can see about 2 to 6 new connections for each new combination.
btw: I also tried to switch off the "enhanced meta data" feature but still get the issue.
Petebro I turned off the metadata preview feature, restarted desktop, and created a report with six visuals and one slicer. With each slicer change my connections increased by 6 connections even with the "enhanced meta data" off. So I am seeing the same things as Anonymous.
I've worked on this issue with the support. Issue number is 121020321001710.
There is a demo dashboard with Adventure Works Tabular Model and some slicers and filters.
We've fixed the issue by increasing
<MaxCatalogConnectionPoolSizePerProcess> to 500.ChrisMuthmann Thanks for the response. I will increase the pool size to 500. But it seems like that could still be reached quickly with a small to medium-size company. If you have 20 employees and they use a report with 8 to 10 visuals on it. You get to 160 to 200 connections very quickly. With a few filter or slicer changes, you are at 500. Is this a temporary solution until they fix the issue?
This should be a temporary solution. I've heard that the support is collecting the issues to decide how important that bugfix is. At least they will clarify the parameter in the documentation of the next version.
We have just tested with a few developers our most critical dashboard. One user can reach approx. 130 connections in 2 minutes. Four users could not reach more than 246 connections. So it is not an easy calculation where you can multiply the dashboard, visuals and filters by the number of users. If 500 is not enough, we can improve the value to 1000. I've not seen a real impact on memory or other resources.