After a nice holiday by the coast I return to find the dreaded close statement error has cropped up again when scrolling down in one of our tables.
Here are a couple of things you can try :
1) In the weblogic console (http://localhost:7101/console) your datasource JDBC\Data Sources\Your Datasource on the connection pool tab set Driver Class Name: oracle.jdbc.driver.OracleDriver and save and restart wl. The XA driver does not always work with ADF in all cases better not to use it.
2) If you are using proxying turn off the weblogic statement cache.(same tab Statement Cache Size: 0)
Here are a couple of things you can try :
1) In the weblogic console (http://localhost:7101/console) your datasource JDBC\Data Sources\Your Datasource on the connection pool tab set Driver Class Name: oracle.jdbc.driver.OracleDriver and save and restart wl. The XA driver does not always work with ADF in all cases better not to use it.
2) If you are using proxying turn off the weblogic statement cache.(same tab Statement Cache Size: 0)
Comments
Post a Comment