Community
Participate
Working Groups
Build Identifier: 3.4.1 Reports that run with no errors in the RCP designer throw the following message when invoked from a Tomcat-based application: May 19, 2010 1:07:14 PM org.eclipse.birt.data.engine.odaconsumer.Connection setOdaQuerySpec INFO: Ignoring UnsupportedOperationException thrown by ODA driver (org.eclipse.birt.report.data.oda.jdbc); cannot set query specification before prepare. The message appears once for every dataset execution in the report. This is observed both in a report using oracle.jdbc.driver.OracleDriver, using oracle.jdbc.OracleDriver and a Derby-based report using org.eclipse.birt.report.data.oda.sampledb.Driver Note that the anticipated data is returned to the report; the only known effect is the appearance in the log of these messages. I'm classifying this as Minor but only because I can'r prove there are serious side effects involved. Reproducible: Always Steps to Reproduce: 1. Create a report 2. Invoke it from an Apache Tomcat 6.0.20-based application 3. View the log
Created attachment 169191 [details] Sample report that works in RCP but throws the error in Tomcat app
The log message prefix, "INFO: ", indicates that this is an informational message only; i.e. not an error, in fact not even a warning. It has no impact on the results of the report output. FYI, the message's logging level has been further lowered to FINE in BIRT 2.5.3.
