iPortal Connection closing problem

Hi, 
 
I have a relatively complex report, when i deploy the report on iPortal it works for the first time.(throwing org.eclipse.birt.report.data.oda.jdbc.JDBCException: Failed to close the connection. 
SQL error #1: Io exception: Socket close) 
 
After that whenever i try to open the report i get the error that my crosstab datacube bindings are lost (Column binding "ROW_DETAIL_ID/ROWTABLEFIELDTYPE" has referred to a data set column "ROWTABLEFIELDTYPE" which does not exist. 
Column binding "ROW_DETAIL_ID/ROWTABLEFIELDTYPE" has referred to a data set column "ROWTABLEFIELDTYPE" which does not exists). 
 
The report also give problems when viewed with BIRT web viewer. (First time it runs fine then next says that olap/cube_Data Cube - tableTypeResponses doesnt exist) 
 
I have noticed that this problem occurs when there is large amount of data in the reports. 
 
We are using dynamic connection profile method for connection. 
 
Version Info 
The Eclipse BIRT designer version we use is "Eclipse BIRT Designer Version 2.2.2.r222_v20071226 Build <2.2.2.v20080317-0630>" 
 
And the Actuate iPortal version is 9 Service Pack 3 Fix 3 (Build 90F080320)

Find more posts tagged with

Comments

Virgil Dodson

Hi amit5094, 
 
What database are you using? Have you tried a different version of the driver? Also, does this happen only once deployed, or in the web viewer in the designer too? If it happens in the designer too, you might try downloading the BIRT 2.3 designer to see if this was a bug already corrected. If this happens only in the iPortal, then I would try downloading the latest beta version of iPortal available with the Actuate 10 Beta at the link below. 
 
<a class='bbc_url' href='http://www.birt-exchange.com/wiki/Actuate_10/'>Actuate 10 - BIRT Wiki - BIRT Exchange</a>

amit5094

Hi Vigil,

Database - Oracle 10g Enterprise edition release 10.2.0.1.0
latest JDBC Driver for the same version ojdbc14.jar

I tried using BIRT 2.3 and the report was working fine in it (But then those reports are not supported in iPortal 9). Driver is not a problem as the report is working fine with the same driver in BIRT 2.3.
Seems the problem is with BIRT 2.2.1 and iPortal 9.

The repeated exception that i see in the logs is
Nov 26, 2008 5:24:26 PM org.eclipse.birt.data.engine.odaconsumer.Connection close
SEVERE: Cannot close connection.
org.eclipse.birt.report.data.oda.jdbc.JDBCException: Failed to close the connection.
SQL error #1: Io exception: Socket closed
;
java.sql.SQLException: Io exception: Socket closed
at org.eclipse.birt.report.data.oda.jdbc.Connection.close(Connection.java:301)
at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaConnection.close(OdaConnection.java:333)
at org.eclipse.birt.data.engine.odaconsumer.Connection.close(Connection.java:177)
at org.eclipse.birt.data.engine.executor.DataSource.close(DataSource.java:285)
at org.eclipse.birt.data.engine.executor.DataSource.finalize(DataSource.java:304)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
Caused by: java.sql.SQLException: Io exception: Socket closed
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:480)
at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:1175)
at org.eclipse.birt.report.data.oda.jdbc.Connection.close(Connection.java:297)
... 8 more

As far as Actuate 10 is concerned, i am not sure that will help because we are using Actuate 9 in our production server.

By the way i was checking through my DBA, Actuate 9 and BIRT 2.2 both left lots of open connections in Database... which became inactive after a few seconds.

Is there a workaround through which i can avoid this problem... The report is not that complex (attaching the same)...

Many thanks,
Amit

Virgil Dodson

Hi Amit, one workaround would be to use the Oracle driver directly with the report rather than using the connection profile. I'm glad to see this is working correctly with BIRT 2.3 which means it should work better with Actuate 10 which supports BIRT 2.3 reports. Since you have Actuate 9 in production, you should also contact Actuate Support to see if they have any other workarounds they can offer.

amit5094

Hi Vigil, 
 
As per your suggestion for a workaround i tried to pass the driver information in the hardcoded without using the connection profile, the problem still persisted. 
 
Few queries:- 
[1] Could the problem could be because of the way connections are handled by BIRT and iPortal in the datacube. since i have a datacube in my report and use it at many places with the use of filter. Some thing like sub reports. 
 
[2] Also there like 4 levels of queries being made in the report. Could that be a problem, 
 
QueryA 
--QueryBwithparametersOfResultA

QueryCwithparametersOfResultB

QueryDwithparametersOfResultC,B

QueryEwithparametersOfResultC,B

CrosstabFwithParametersOfesultC,B 
 
 
[3] Is there anyway possible for us not execute a report item (as an alternate solution to the visibility property). 
 
 
Many thanks, 
Amit Jain.