nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Open cursors in database by report's querys

MOnita

My dba point to me that the performance of my system was decreasing because some "open cursors" which I interpret as open connections. After check on the querys I get to know that those open connections where not from my java EE aplication entities or something but from the BIRT report's querys...I guess users are clicking on the "generate report" and losing the application but not logging out or something, is there a way to making BIRT know about this and close the connection? Am I misunderstanding something in integrating BIRT reporting with my JAVA EE application?
 
Thank you in advance.

Find more posts tagged with

Comments

Clement Wong

Connections are typically closed based on the default timeout value, but we will need more information to assist you.
 
1. What version of BIRT are you using?
2. What application server and version did you use to deploy BIRT?
3. What database and version does your BIRT reports connect to?
4. What JDBC driver is defined in your report? What version is the JDBC driver?

MOnita

<blockquote class="ipsBlockquote" data-author="Clement Wong" data-cid="141898" data-time="1453750867">
<div>
I'm sorry you're right, I mus provide more info.
 
1. What version of BIRT are you using? Eclipse BIRT Designer Version 4.2.1.v201209101448 Build <4.2.1.v20120918-1113>
2. What application server and version did you use to deploy BIRT? glassfish 4.1
3. What database and version does your BIRT reports connect to? oracle 11g
4. What JDBC driver is defined in your report? What version is the JDBC driver? oracle.jdbc.driver.OracleDriver v10.2 ---> ojdbc14.jar
</div>
</blockquote>
I've also set on this report the timeout for each dataset use but it doesn't seem to change anything.
 They said these log entries could be also because of this : 
 
 
<div>
<pre class="_prettyXprint">
!ENTRY org.eclipse.e4.ui.workbench 4 0 2016-01-22 13:01:14.973
!MESSAGE Unable to retrieve the bundle from the URI: bundleclass://org.eclipse.e4.ui.workbench.addons.swt/org.eclipse.e4.ui.workbench.addons.minmax.MinMaxAddon
!SESSION 2016-01-26 10:19:25.725

eclipse.buildId=unknown
java.version=1.8.0_51
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_MX
Framework arguments: \\[report path].rptdesign
Command-line arguments: -os win32 -ws win32 -arch x86 \\[report path].rptdesign</pre>
and: 
 
<div>
<pre class="_prettyXprint">
org.eclipse.birt.report.service.api.ReportServiceException: Failed to open the report document.
at org.eclipse.birt.report.service.ReportEngineService.throwDummyException(ReportEngineService.java:1114)
at org.eclipse.birt.report.service.ReportEngineService.openReportDocument(ReportEngineService.java:511)
at org.eclipse.birt.report.service.BirtViewerReportService.openReportDocument(BirtViewerReportService.java:269)
at org.eclipse.birt.report.service.BirtViewerReportService.getResultSetsMetadata(BirtViewerReportService.java:543)
at org.eclipse.birt.report.service.actionhandler.AbstractQueryExportActionHandler.__execute(AbstractQueryExportActionHandler.java:97)
at org.eclipse.birt.report.service.actionhandler.AbstractBaseActionHandler.execute(AbstractBaseActionHandler.java:90)
at org.eclipse.birt.report.soapengine.processor.AbstractBaseDocumentProcessor.__executeAction(AbstractBaseDocumentProcessor.java:47)
at org.eclipse.birt.report.soapengine.processor.AbstractBaseComponentProcessor.executeAction(AbstractBaseComponentProcessor.java:143)
at org.eclipse.birt.report.soapengine.processor.BirtDocumentProcessor.handleQueryExport(BirtDocumentProcessor.java:155)
at sun.reflect.GeneratedMethodAccessor2808.invoke(Unknown Source)</pre>
I'm not sure if one does affect the other...
Thank you in advance.
</div>
</div>

jar

I am no DBA but if you mean with "open cursor" that a transaction on the DB is opened and not closed ... read on :-)
 
We had an issue with postgresql opening a transaction when executing a select query from BIRT and it stayed open.
 
This sometimes resulted in blocked proces as a new report was waiting for the former transaction to close. In the connectionSettings for our PSQL database in the BIRT report we set the AutoCommit option to true and no open transactions anymore (and blocking processes ...).
 
I have no experience with Oracle but might be related.
 
Jeroen

Clement Wong

Jeroen makes a good point.
 
For each of your reports (or if you are using a library), in your Data Source > Properties > Advanced (see screenshot), change the Auto Commit from Auto to True.
 
See attached screenshot for default value:

MOnita

Thank you to both of you!, I'm going to try this and let you know how it goes.