index-authority -o

[molly mcmanus]

We are using dspace 5.3, linux, oracle and are getting an error each night when we run the index-authority -o


The error we are getting is below. Is this due to memory or something we have set up incorrectly?

Thanks, Molly

Exception: null

java.lang.StackOverflowError

                at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)

                at java.net.SocketInputStream.read(SocketInputStream.java:171)

                at java.net.SocketInputStream.read(SocketInputStream.java:141)

                at oracle.net.ns.Packet.receive(Packet.java:308)

                at oracle.net.ns.DataPacket.receive(DataPacket.java:106)

                at oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:324)

                at oracle.net.ns.NetInputStream.read(NetInputStream.java:268)

                at oracle.net.ns.NetInputStream.read(NetInputStream.java:190)

                at oracle.net.ns.NetInputStream.read(NetInputStream.java:107)

                at

oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInpu

tStreamWrapper.java:124)

                at

oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWra

pper.java:80)

                at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1137)

                at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:350)

                at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)

                at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)

                at

oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:2

08)

                at

oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement

.java:1046)

                at

oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.jav

a:1207)

                at

oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.jav

a:1296)

                at

oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedSt

atement.java:3613)

                at

oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedState

ment.java:3657)

                at

oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePrepar

edStatementWrapper.java:1495)

                at

org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Delegating

PreparedStatement.java:96)

                at

org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Delegating

PreparedStatement.java:96)

                at

org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Delegating

PreparedStatement.java:96)

                at

org.dspace.storage.rdbms.DatabaseManager.queryTable(DatabaseManager.java:23

4)

                at

org.dspace.content.DSpaceObject$MetadataCache.retrieveMetadata(DSpaceObject

.java:1330)

                at

org.dspace.content.DSpaceObject$MetadataCache.get(DSpaceObject.java:1265)

                at org.dspace.content.DSpaceObject.getMetadata(DSpaceObject.java:676)

                at org.dspace.content.DSpaceObject.getMetadata(DSpaceObject.java:585)

                at

org.dspace.content.DSpaceObject.getMetadataByMetadataString(DSpaceObject.ja

va:643)

                at

org.dspace.authority.indexer.DSpaceAuthorityIndexer.hasMore(DSpaceAuthority

Indexer.java:130)

                at

org.dspace.authority.indexer.DSpaceAuthorityIndexer.hasMore(DSpaceAuthority

Indexer.java:159)

                at

org.dspace.authority.indexer.DSpaceAuthorityIndexer.hasMore(DSpaceAuthority

Indexer.java:159)

                at

org.dspace.authority.indexer.DSpaceAuthorityIndexer.hasMore(DSpaceAuthority

Indexer.java:159)

[Chris Gray]

We ran into this problem.

The account that runs dspace may have its login profile configured to set the Java variables (JAVA_OPTS) needed to give the account more memory than the default, so the [dspace]/bin/dspace scripts run fine from the command line, but the login profile is not used by cronjobs.

For us the problem was solved by adding a line setting the JAVA_OPTS environment variable near the beginning of our crontab. Just repeat the JAVA_OPTS line that is in the account's .profile file. An "export" command is not needed since the environment variable is only needed for the duration of the crontab script.

Chris