While refreshing a report I am getting connection error due to maxing
out of connections in connection pool on the database server.
Tried all 3 available following options for connection pool mode on the
corresponding universe parameter connection configuration.
Disconnect after each transaction
Keep the connection active for x minutes
Keep the connection active for whole session (local mode only)
It seems that while refreshing a report, each data provider opens a new
connection to the database and never drops the connection even after
the refresh completes.
Please let me know if we need to do some other settings or any other
work around for this issue.
If you have multiple data providers, or sub reports for that matter, there may not be much you can do about it except either increase the number of connections you can have to the database or reduce the number of data providers in the report.
We had a situation where we were maxing out the connections to an Oracle database. We had a report with 14 sub reports that was scheduled over 300 times at once. It was overloading the connections to the database. We resolved this by restricting the report to only run on one of our job servers so it limited the number of reports that could run at one time. This may not help your in your case though.
John, Thanks for the response but it w’not serve my purpose.
I am looking for a way to drop those INACTIVE connections immediately automatically after the refresh of the report.
However we have figured out that if we set the value (in minutes) for a certain paramater in BO Connection Server then those INACTIVE connections get dropped by server’s garbage collector after that duration (in minutes).
SAP BO has accepted this issue as a BUG. Waiting for their fix.
If you set the Connection Pool Mode to “Disconnect after each transaction”, then it should do just that. Are you saying that it doesn’t?
Also just to clarify, if you set the Connection Pool Mode to “Keep the connection active for” and set the pool time out to lets say 10 minutes, then the connection remains open for 10 minutes. As I understand it, the 10 minutes is 10 minutes of idle time. If within this time the connection is re-used by another session, then the 10 minutes starts over again after the query for that session has ended.
SAP BO engineer was able to simulate this issue and has recognized this issue as a bug in 3-tier environment.
SAP BO engineer suggested following solution…
a. Set the “Max Pool Time” to 0 in the cs.cfg file, and
b. Set Idle Connection Timeout (minutes): 0 in the Cmc -> ConnectionServer property,
c. Restart the ConnectionServer.
Good News was that this solution worked…and at the same time they retreated from their earlier recogniziton of this issue as a bug and stated that this is normal functionality.
While investigating the issue with SAP BO engineer, I found out that my machine only had BOXI R3.1 Client installed on it and does not have SP2 installed successfully.
On BOXI Server side it had BOXI R3.1 SP2 FP2.5 installed.
For my client machine, it was still an issue even after implemnting the SAP BO solution.
But when I installed SP2 on my client machine then issue was resolved.
According to SAP BO engineer…
“The main thing is that the BO XI3.1 server and the clients need to be on the same product version; otherwise, the deski full client may not behave correctly.”
(BOB member since 2002-08-15)
(BOB member since 2002-09-13)