I have written a report that contains an on-demand subreport. The data connection is a JDBC database connection. When viewing the report in InfoView and monitoring my database connections, I noticed that the data connection stays open, even after the report has been closed in InfoView. In fact, the connection persists after the viewing user has logged off of InfoView. The data connection does not close until the designated 20 minutes to keep idle connections open has expired (a setting in the Page Server).
I thought the expected behavior was for the connection to close after the main report data had been fetched, and then reopen for any subreport requests. Even if this is not the case, the data connection should at least close after the report has been closed in InfoView.
Has anyone else encountered this problem? It is an issue because we have a limited number of client driver licences, and these data connections can not stick around for 20 minutes until BOE decides to end them.
I have not found any assistance for this issue nor have I found a solution myself. I’d say it’s just lazy connection management by BOE.
I haven’t found any tools or anything that would let me view open database connections that BOE is keeping, either. I also haven’t been able to come up with any CMS queries that would allow me to view data source connections. Any of these things would be helpful.
Actually, in my case it is happening only with one report. Every time the report runs through InfoView, two new lazy connections are created and gets multiplied on every run.
So just wondering why only on specific report and not all other reports.
Does anyone have a solution to this issue? I’m running on demand crystal reports against a universe. Some reports contain sub-queries while others do not. Eventually the reports start to fail and have to restart the page server.
(BOB member since 2002-08-08)
(BOB member since 2005-08-04)
(BOB member since 2010-09-13)