Hi Folks,
Very occasionally we see the following error on DSpace 1.5.2, when
calling Item.find(). Has anyone else seen something similar, and have
any idea what might be going on?
Caused by: java.sql.SQLException: Exhausted Resultset
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:208)
at
oracle.jdbc.driver.OracleResultSetImpl.getBytes(OracleResultSetImpl.java:699)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:203)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:203)
at
org.dspace.storage.rdbms.DatabaseManager.process(DatabaseManager.java:1132)
at
org.dspace.storage.rdbms.TableRowIterator.next(TableRowIterator.java:151)
at org.dspace.content.Item.<init>(Item.java:150)
at org.dspace.content.Item.find(Item.java:242)
at
uk.co.symplectic.publications.repo.dspace15x.process.ItemManager.oneCopyArchived(ItemManager.java:277)
... 21 more
(The last line here is my own code calling into the DSpace API)
>From what I can find online for this error, it's usually due to some problem
>with not calling next() on the result set in the database layer, or closing
>the prepared statement before reading from it. That would make sense if this
>were a consistent problem, but since we can't reliably reproduce it, it seems
>unlikely.
Any thoughts gratefully received.
Cheers,
Richard
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
