Using JRC from Eclipse 2 version for generation of reports using Crystal Reports from a Java J2EE application
Environment is WebSphere Application Server 7.0, DB2 9.5 and most recent download of CR Java runtime version (crjava-runtime_12.2.212.zip)
The code that calls Crystal Reports sets up the parameters for CR to use the data source defined to WebSphere. It appears to connect to the database OK using JNDI , but fails in the following call.
clientDoc.getDatabaseController().setTableLocation(origTable,newTable);
The problem appears to be that a commit is being done by the JDBCConnection code. (see stack trace). Since the CR interface code is within an EJB, there is a container managed transaction. Looks like Websphere does not like the connection being closed manually when it is within it's transaction context.
Caused by: java.sql.SQLException: DSRA9350E: Operation Connection.commit is not allowed during a global transaction.
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.commit(WSJdbcConnection.java:1062)
at com.crystaldecisions.reports.queryengine.driverImpl.jdbc.JDBCConnection.try(Unknown Source)
Is this a supported configuration? Any idea how to prevent the CR Java code from closing the connection ?
P.S. This code runs well on version 1 of the JRC (crystalreports-javasdk-11.8.8.zip). The only reason I am testing on CR for Eclipse 2 is I can't figure out how to get rid of the nag on the footer of reports produced (Please register etc . . .)
Any assistance would be appreciated.
Thanks
Frank