Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313603

Summary: BIRT 2.5.0 reports in Tomcat 6.0.20 throw UnsupportedOperationException
Product: z_Archived Reporter: Richard A. Polunsky <rpolunsky>
Component: BIRTAssignee: Birt-DataAccess <Birt-DataAccess-inbox>
Status: RESOLVED INVALID QA Contact:
Severity: minor    
Priority: P3 CC: lchan
Version: unspecified   
Target Milestone: 2.5.3   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Sample report that works in RCP but throws the error in Tomcat app none

Description Richard A. Polunsky CLA 2010-05-19 14:56:13 EDT 
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
Comment 1 Richard A. Polunsky CLA 2010-05-19 14:58:45 EDT 
Created attachment 169191 [details]
Sample report that works in RCP but throws the error in Tomcat app
Comment 2 Linda Chan CLA 2010-05-19 18:42:11 EDT 
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.