You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Sa...@bosch-si.com on 2011/07/11 13:36:43 UTC
Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
Hi all,
we are currently facing a problem with Jackrabbit 1.6.2 and Oracle
10.4.0.2 when trying to add new nodes. We are embedding jackrabbit in
our application and running on a WebSphere 6.1 application server.
The stacktrace is:
ERROR BundleDbPersistenceManager - failed to write bundle:
abf3ffc7-16eb-4b2a-b22b-756ec9d078e4
java.sql.SQLException: Io exception: Checksum fail
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:12
5)
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:16
2)
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:27
4)
at
oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStat
ement.java:646)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.
java:1081)
at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrepare
dStatement.java:2905)
at
oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStateme
nt.java:2996)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmtInternal(ConnectionRecoveryManager.java:371)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmtInternal(ConnectionRecoveryManager.java:298)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmt(ConnectionRecoveryManager.java:261)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmt(ConnectionRecoveryManager.java:239)
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.storeBundle(BundleDbPersistenceManager.java:1247)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.putBundle(AbstractBundlePersistenceManager.java:711)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.storeInternal(AbstractBundlePersistenceManager.java:651)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.store(AbstractBundlePersistenceManager.java:515)
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.store(BundleDbPersistenceManager.java:568)
at
org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(Share
dItemStateManager.java:741)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedIte
mStateManager.java:1160)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
tateManager.java:351)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
tateManager.java:326)
at
org.apache.jackrabbit.core.version.AbstractVersionManager$WriteOperation
.save(AbstractVersionManager.java:189)
at
org.apache.jackrabbit.core.version.AbstractVersionManager.createVersionH
istory(AbstractVersionManager.java:369)
at
org.apache.jackrabbit.core.version.VersionManagerImpl$1.run(VersionManag
erImpl.java:215)
at
org.apache.jackrabbit.core.version.VersionManagerImpl$DynamicESCFactory.
doSourced(VersionManagerImpl.java:580)
at
org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHisto
ry(VersionManagerImpl.java:212)
at
org.apache.jackrabbit.core.version.XAVersionManager.createVersionHistory
(XAVersionManager.java:157)
at
org.apache.jackrabbit.core.version.AbstractVersionManager.getVersionHist
ory(AbstractVersionManager.java:273)
at
org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:7
38)
at
org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1097)
at
org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:915)
...
That problem occurs with a complete fresh installation of jackrabbit.
The strange thing is that some nodes could be added while others fail
with the above exception. I also saw the following error log from
jackrabbit:
ERROR ConnectionRecoveryManager - could not execute statement, reason:
E/A-Exception: Checksum fail, state/code: null/17002
ERROR ConnectionRecoveryManager - could not execute statement, reason:
E/A-Exception: Checksum fail, state/code: null/17002
ERROR ConnectionRecoveryManager - failed to close connection, reason:
Getrennte Verbindung, state/code: null/17008
ERROR ConnectionRecoveryManager - failed to close connection, reason:
Getrennte Verbindung, state/code: null/17008
Our complete environment is:
Java VM:
--------------------------
java version "1.5.0_24"
Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_24-b02
20100703 solaris sparc (SR12))
Java HotSpot(TM) Server VM (build 1.5.0_24-b02, mixed mode)
IBM Java ORB build orb50-20100629
XML build XSLT4J Java 2.7.19
XML build IBM JAXP 1.3.11
XML build XML4J 4.4.19
Database:
---------------------------
- Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bit
Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining
options
App Server:
---------------------------
Websphere ist Version 6.1.0.33.
JDBC driver:
---------------------------
ojdbc4.jar (10.1.0.4.0) for Java 1.4
Anybody an idea? I stick with that exception. I have already googled for
the specific error code or stack but I didn`t find anything. Any help is
appreciated!
Best regards
Sascha
AW: AW: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
Posted by Sa...@bosch-si.com.
Just for your info. I have finally got it working. Problem was the ojdbc14 driver in version 10.1.0.4.0 together with Solaris Sparc. I have updated the oracle driver to the 10.2 release and now it works. But the problem really only occurs with that constellation. Other constellations, x86 with ojdbc14 driver 10.1.0.4.0, are working.
-----Ursprüngliche Nachricht-----
Von: Sascha.Theves@bosch-si.com [mailto:Sascha.Theves@bosch-si.com]
Gesendet: Dienstag, 12. Juli 2011 11:23
An: users@jackrabbit.apache.org
Betreff: AW: AW: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
No nothing, or nothing related to exactly the issue here. I found some oracle errors for 17002 but that has something to do with the TNSListener not correctly set up. But that seems not to be our problem because we are able to start jackrabbit and we are also able to add some nodes. But a few one fail. Sometimes it is when creating the version history in jackrabbit sometimes it has to do with the DataStore. I thought it has to do with the size of the blob but it seems that is not the reason because sometimes it fails with very small blobs too. Very strange. I think we do not get the complete/real failure message from the oracle driver but we cannot switch that because it runs in a production environment and we are not the only one who uses that database.
-----Ursprüngliche Nachricht-----
Von: Thomas Mueller [mailto:mueller@adobe.com]
Gesendet: Dienstag, 12. Juli 2011 11:14
An: users@jackrabbit.apache.org
Betreff: Re: AW: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
Hi,
Did you find anything on Google?
Regards,
Thomas
On 7/12/11 10:35 AM, "Sascha.Theves@bosch-si.com"
<Sa...@bosch-si.com> wrote:
>Nobody an idea here? Seems that it happens when trying to persist oracle
>blobs...
>
>-----Ursprüngliche Nachricht-----
>Von: Sascha.Theves@bosch-si.com [mailto:Sascha.Theves@bosch-si.com]
>Gesendet: Montag, 11. Juli 2011 13:37
>An: users@jackrabbit.apache.org
>Betreff: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new
>node
>
>Hi all,
>
>
>
>we are currently facing a problem with Jackrabbit 1.6.2 and Oracle
>10.4.0.2 when trying to add new nodes. We are embedding jackrabbit in
>our application and running on a WebSphere 6.1 application server.
>
>
>
>The stacktrace is:
>
>
>
>ERROR BundleDbPersistenceManager - failed to write bundle:
>abf3ffc7-16eb-4b2a-b22b-756ec9d078e4
>
>java.sql.SQLException: Io exception: Checksum fail
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:12
>5)
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:16
>2)
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:27
>4)
>
> at
>oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStat
>ement.java:646)
>
> at
>oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.
>java:1081)
>
> at
>oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrepare
>dStatement.java:2905)
>
> at
>oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStateme
>nt.java:2996)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmtInternal(ConnectionRecoveryManager.java:371)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmtInternal(ConnectionRecoveryManager.java:298)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmt(ConnectionRecoveryManager.java:261)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmt(ConnectionRecoveryManager.java:239)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
>.storeBundle(BundleDbPersistenceManager.java:1247)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.putBundle(AbstractBundlePersistenceManager.java:711)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.storeInternal(AbstractBundlePersistenceManager.java:651)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.store(AbstractBundlePersistenceManager.java:515)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
>.store(BundleDbPersistenceManager.java:568)
>
> at
>org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(Share
>dItemStateManager.java:741)
>
> at
>org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedIte
>mStateManager.java:1160)
>
> at
>org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
>tateManager.java:351)
>
> at
>org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
>tateManager.java:326)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager$WriteOperation
>.save(AbstractVersionManager.java:189)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager.createVersionH
>istory(AbstractVersionManager.java:369)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl$1.run(VersionManag
>erImpl.java:215)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl$DynamicESCFactory.
>doSourced(VersionManagerImpl.java:580)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHisto
>ry(VersionManagerImpl.java:212)
>
> at
>org.apache.jackrabbit.core.version.XAVersionManager.createVersionHistory
>(XAVersionManager.java:157)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager.getVersionHist
>ory(AbstractVersionManager.java:273)
>
> at
>org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:7
>38)
>
> at
>org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1097)
>
> at
>org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:915)
>
> ...
>
>
>
>That problem occurs with a complete fresh installation of jackrabbit.
>The strange thing is that some nodes could be added while others fail
>with the above exception. I also saw the following error log from
>jackrabbit:
>
>
>
>ERROR ConnectionRecoveryManager - could not execute statement, reason:
>E/A-Exception: Checksum fail, state/code: null/17002
>
>ERROR ConnectionRecoveryManager - could not execute statement, reason:
>E/A-Exception: Checksum fail, state/code: null/17002
>
>ERROR ConnectionRecoveryManager - failed to close connection, reason:
>Getrennte Verbindung, state/code: null/17008
>
>ERROR ConnectionRecoveryManager - failed to close connection, reason:
>Getrennte Verbindung, state/code: null/17008
>
>
>
>Our complete environment is:
>
>
>
>
>
>Java VM:
>
>--------------------------
>
>java version "1.5.0_24"
>
>
>
>Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_24-b02
>20100703 solaris sparc (SR12))
>
>
>
>Java HotSpot(TM) Server VM (build 1.5.0_24-b02, mixed mode)
>
>
>
>IBM Java ORB build orb50-20100629
>
>
>
>XML build XSLT4J Java 2.7.19
>
>
>
>XML build IBM JAXP 1.3.11
>
>
>
>XML build XML4J 4.4.19
>
>
>
>
>
>Database:
>
>---------------------------
>
>- Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bit
>Production
>
>With the Partitioning, Oracle Label Security, OLAP and Data Mining
>options
>
>
>
>
>
>App Server:
>
>---------------------------
>
>
>
>Websphere ist Version 6.1.0.33.
>
>
>
>JDBC driver:
>
>---------------------------
>
>
>
>ojdbc4.jar (10.1.0.4.0) for Java 1.4
>
>
>
>Anybody an idea? I stick with that exception. I have already googled for
>the specific error code or stack but I didn`t find anything. Any help is
>appreciated!
>
>
>
>Best regards
>
>
>
>Sascha
>
>
>
AW: AW: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
Posted by Sa...@bosch-si.com.
No nothing, or nothing related to exactly the issue here. I found some oracle errors for 17002 but that has something to do with the TNSListener not correctly set up. But that seems not to be our problem because we are able to start jackrabbit and we are also able to add some nodes. But a few one fail. Sometimes it is when creating the version history in jackrabbit sometimes it has to do with the DataStore. I thought it has to do with the size of the blob but it seems that is not the reason because sometimes it fails with very small blobs too. Very strange. I think we do not get the complete/real failure message from the oracle driver but we cannot switch that because it runs in a production environment and we are not the only one who uses that database.
-----Ursprüngliche Nachricht-----
Von: Thomas Mueller [mailto:mueller@adobe.com]
Gesendet: Dienstag, 12. Juli 2011 11:14
An: users@jackrabbit.apache.org
Betreff: Re: AW: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
Hi,
Did you find anything on Google?
Regards,
Thomas
On 7/12/11 10:35 AM, "Sascha.Theves@bosch-si.com"
<Sa...@bosch-si.com> wrote:
>Nobody an idea here? Seems that it happens when trying to persist oracle
>blobs...
>
>-----Ursprüngliche Nachricht-----
>Von: Sascha.Theves@bosch-si.com [mailto:Sascha.Theves@bosch-si.com]
>Gesendet: Montag, 11. Juli 2011 13:37
>An: users@jackrabbit.apache.org
>Betreff: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new
>node
>
>Hi all,
>
>
>
>we are currently facing a problem with Jackrabbit 1.6.2 and Oracle
>10.4.0.2 when trying to add new nodes. We are embedding jackrabbit in
>our application and running on a WebSphere 6.1 application server.
>
>
>
>The stacktrace is:
>
>
>
>ERROR BundleDbPersistenceManager - failed to write bundle:
>abf3ffc7-16eb-4b2a-b22b-756ec9d078e4
>
>java.sql.SQLException: Io exception: Checksum fail
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:12
>5)
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:16
>2)
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:27
>4)
>
> at
>oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStat
>ement.java:646)
>
> at
>oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.
>java:1081)
>
> at
>oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrepare
>dStatement.java:2905)
>
> at
>oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStateme
>nt.java:2996)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmtInternal(ConnectionRecoveryManager.java:371)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmtInternal(ConnectionRecoveryManager.java:298)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmt(ConnectionRecoveryManager.java:261)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmt(ConnectionRecoveryManager.java:239)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
>.storeBundle(BundleDbPersistenceManager.java:1247)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.putBundle(AbstractBundlePersistenceManager.java:711)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.storeInternal(AbstractBundlePersistenceManager.java:651)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.store(AbstractBundlePersistenceManager.java:515)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
>.store(BundleDbPersistenceManager.java:568)
>
> at
>org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(Share
>dItemStateManager.java:741)
>
> at
>org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedIte
>mStateManager.java:1160)
>
> at
>org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
>tateManager.java:351)
>
> at
>org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
>tateManager.java:326)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager$WriteOperation
>.save(AbstractVersionManager.java:189)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager.createVersionH
>istory(AbstractVersionManager.java:369)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl$1.run(VersionManag
>erImpl.java:215)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl$DynamicESCFactory.
>doSourced(VersionManagerImpl.java:580)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHisto
>ry(VersionManagerImpl.java:212)
>
> at
>org.apache.jackrabbit.core.version.XAVersionManager.createVersionHistory
>(XAVersionManager.java:157)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager.getVersionHist
>ory(AbstractVersionManager.java:273)
>
> at
>org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:7
>38)
>
> at
>org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1097)
>
> at
>org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:915)
>
> ...
>
>
>
>That problem occurs with a complete fresh installation of jackrabbit.
>The strange thing is that some nodes could be added while others fail
>with the above exception. I also saw the following error log from
>jackrabbit:
>
>
>
>ERROR ConnectionRecoveryManager - could not execute statement, reason:
>E/A-Exception: Checksum fail, state/code: null/17002
>
>ERROR ConnectionRecoveryManager - could not execute statement, reason:
>E/A-Exception: Checksum fail, state/code: null/17002
>
>ERROR ConnectionRecoveryManager - failed to close connection, reason:
>Getrennte Verbindung, state/code: null/17008
>
>ERROR ConnectionRecoveryManager - failed to close connection, reason:
>Getrennte Verbindung, state/code: null/17008
>
>
>
>Our complete environment is:
>
>
>
>
>
>Java VM:
>
>--------------------------
>
>java version "1.5.0_24"
>
>
>
>Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_24-b02
>20100703 solaris sparc (SR12))
>
>
>
>Java HotSpot(TM) Server VM (build 1.5.0_24-b02, mixed mode)
>
>
>
>IBM Java ORB build orb50-20100629
>
>
>
>XML build XSLT4J Java 2.7.19
>
>
>
>XML build IBM JAXP 1.3.11
>
>
>
>XML build XML4J 4.4.19
>
>
>
>
>
>Database:
>
>---------------------------
>
>- Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bit
>Production
>
>With the Partitioning, Oracle Label Security, OLAP and Data Mining
>options
>
>
>
>
>
>App Server:
>
>---------------------------
>
>
>
>Websphere ist Version 6.1.0.33.
>
>
>
>JDBC driver:
>
>---------------------------
>
>
>
>ojdbc4.jar (10.1.0.4.0) for Java 1.4
>
>
>
>Anybody an idea? I stick with that exception. I have already googled for
>the specific error code or stack but I didn`t find anything. Any help is
>appreciated!
>
>
>
>Best regards
>
>
>
>Sascha
>
>
>
Re: AW: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a
new node
Posted by Thomas Mueller <mu...@adobe.com>.
Hi,
Did you find anything on Google?
Regards,
Thomas
On 7/12/11 10:35 AM, "Sascha.Theves@bosch-si.com"
<Sa...@bosch-si.com> wrote:
>Nobody an idea here? Seems that it happens when trying to persist oracle
>blobs...
>
>-----Ursprüngliche Nachricht-----
>Von: Sascha.Theves@bosch-si.com [mailto:Sascha.Theves@bosch-si.com]
>Gesendet: Montag, 11. Juli 2011 13:37
>An: users@jackrabbit.apache.org
>Betreff: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new
>node
>
>Hi all,
>
>
>
>we are currently facing a problem with Jackrabbit 1.6.2 and Oracle
>10.4.0.2 when trying to add new nodes. We are embedding jackrabbit in
>our application and running on a WebSphere 6.1 application server.
>
>
>
>The stacktrace is:
>
>
>
>ERROR BundleDbPersistenceManager - failed to write bundle:
>abf3ffc7-16eb-4b2a-b22b-756ec9d078e4
>
>java.sql.SQLException: Io exception: Checksum fail
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:12
>5)
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:16
>2)
>
> at
>oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:27
>4)
>
> at
>oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStat
>ement.java:646)
>
> at
>oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.
>java:1081)
>
> at
>oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrepare
>dStatement.java:2905)
>
> at
>oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStateme
>nt.java:2996)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmtInternal(ConnectionRecoveryManager.java:371)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmtInternal(ConnectionRecoveryManager.java:298)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmt(ConnectionRecoveryManager.java:261)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
>ager.executeStmt(ConnectionRecoveryManager.java:239)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
>.storeBundle(BundleDbPersistenceManager.java:1247)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.putBundle(AbstractBundlePersistenceManager.java:711)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.storeInternal(AbstractBundlePersistenceManager.java:651)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
>anager.store(AbstractBundlePersistenceManager.java:515)
>
> at
>org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
>.store(BundleDbPersistenceManager.java:568)
>
> at
>org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(Share
>dItemStateManager.java:741)
>
> at
>org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedIte
>mStateManager.java:1160)
>
> at
>org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
>tateManager.java:351)
>
> at
>org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
>tateManager.java:326)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager$WriteOperation
>.save(AbstractVersionManager.java:189)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager.createVersionH
>istory(AbstractVersionManager.java:369)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl$1.run(VersionManag
>erImpl.java:215)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl$DynamicESCFactory.
>doSourced(VersionManagerImpl.java:580)
>
> at
>org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHisto
>ry(VersionManagerImpl.java:212)
>
> at
>org.apache.jackrabbit.core.version.XAVersionManager.createVersionHistory
>(XAVersionManager.java:157)
>
> at
>org.apache.jackrabbit.core.version.AbstractVersionManager.getVersionHist
>ory(AbstractVersionManager.java:273)
>
> at
>org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:7
>38)
>
> at
>org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1097)
>
> at
>org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:915)
>
> ...
>
>
>
>That problem occurs with a complete fresh installation of jackrabbit.
>The strange thing is that some nodes could be added while others fail
>with the above exception. I also saw the following error log from
>jackrabbit:
>
>
>
>ERROR ConnectionRecoveryManager - could not execute statement, reason:
>E/A-Exception: Checksum fail, state/code: null/17002
>
>ERROR ConnectionRecoveryManager - could not execute statement, reason:
>E/A-Exception: Checksum fail, state/code: null/17002
>
>ERROR ConnectionRecoveryManager - failed to close connection, reason:
>Getrennte Verbindung, state/code: null/17008
>
>ERROR ConnectionRecoveryManager - failed to close connection, reason:
>Getrennte Verbindung, state/code: null/17008
>
>
>
>Our complete environment is:
>
>
>
>
>
>Java VM:
>
>--------------------------
>
>java version "1.5.0_24"
>
>
>
>Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_24-b02
>20100703 solaris sparc (SR12))
>
>
>
>Java HotSpot(TM) Server VM (build 1.5.0_24-b02, mixed mode)
>
>
>
>IBM Java ORB build orb50-20100629
>
>
>
>XML build XSLT4J Java 2.7.19
>
>
>
>XML build IBM JAXP 1.3.11
>
>
>
>XML build XML4J 4.4.19
>
>
>
>
>
>Database:
>
>---------------------------
>
>- Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bit
>Production
>
>With the Partitioning, Oracle Label Security, OLAP and Data Mining
>options
>
>
>
>
>
>App Server:
>
>---------------------------
>
>
>
>Websphere ist Version 6.1.0.33.
>
>
>
>JDBC driver:
>
>---------------------------
>
>
>
>ojdbc4.jar (10.1.0.4.0) for Java 1.4
>
>
>
>Anybody an idea? I stick with that exception. I have already googled for
>the specific error code or stack but I didn`t find anything. Any help is
>appreciated!
>
>
>
>Best regards
>
>
>
>Sascha
>
>
>
AW: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
Posted by Sa...@bosch-si.com.
Nobody an idea here? Seems that it happens when trying to persist oracle blobs...
-----Ursprüngliche Nachricht-----
Von: Sascha.Theves@bosch-si.com [mailto:Sascha.Theves@bosch-si.com]
Gesendet: Montag, 11. Juli 2011 13:37
An: users@jackrabbit.apache.org
Betreff: Jackrabbit 1.6.2 and Oracle - Checksum failed when adding a new node
Hi all,
we are currently facing a problem with Jackrabbit 1.6.2 and Oracle
10.4.0.2 when trying to add new nodes. We are embedding jackrabbit in
our application and running on a WebSphere 6.1 application server.
The stacktrace is:
ERROR BundleDbPersistenceManager - failed to write bundle:
abf3ffc7-16eb-4b2a-b22b-756ec9d078e4
java.sql.SQLException: Io exception: Checksum fail
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:12
5)
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:16
2)
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:27
4)
at
oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStat
ement.java:646)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.
java:1081)
at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrepare
dStatement.java:2905)
at
oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStateme
nt.java:2996)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmtInternal(ConnectionRecoveryManager.java:371)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmtInternal(ConnectionRecoveryManager.java:298)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmt(ConnectionRecoveryManager.java:261)
at
org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMan
ager.executeStmt(ConnectionRecoveryManager.java:239)
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.storeBundle(BundleDbPersistenceManager.java:1247)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.putBundle(AbstractBundlePersistenceManager.java:711)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.storeInternal(AbstractBundlePersistenceManager.java:651)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.store(AbstractBundlePersistenceManager.java:515)
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.store(BundleDbPersistenceManager.java:568)
at
org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(Share
dItemStateManager.java:741)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedIte
mStateManager.java:1160)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
tateManager.java:351)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemS
tateManager.java:326)
at
org.apache.jackrabbit.core.version.AbstractVersionManager$WriteOperation
.save(AbstractVersionManager.java:189)
at
org.apache.jackrabbit.core.version.AbstractVersionManager.createVersionH
istory(AbstractVersionManager.java:369)
at
org.apache.jackrabbit.core.version.VersionManagerImpl$1.run(VersionManag
erImpl.java:215)
at
org.apache.jackrabbit.core.version.VersionManagerImpl$DynamicESCFactory.
doSourced(VersionManagerImpl.java:580)
at
org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHisto
ry(VersionManagerImpl.java:212)
at
org.apache.jackrabbit.core.version.XAVersionManager.createVersionHistory
(XAVersionManager.java:157)
at
org.apache.jackrabbit.core.version.AbstractVersionManager.getVersionHist
ory(AbstractVersionManager.java:273)
at
org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:7
38)
at
org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1097)
at
org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:915)
...
That problem occurs with a complete fresh installation of jackrabbit.
The strange thing is that some nodes could be added while others fail
with the above exception. I also saw the following error log from
jackrabbit:
ERROR ConnectionRecoveryManager - could not execute statement, reason:
E/A-Exception: Checksum fail, state/code: null/17002
ERROR ConnectionRecoveryManager - could not execute statement, reason:
E/A-Exception: Checksum fail, state/code: null/17002
ERROR ConnectionRecoveryManager - failed to close connection, reason:
Getrennte Verbindung, state/code: null/17008
ERROR ConnectionRecoveryManager - failed to close connection, reason:
Getrennte Verbindung, state/code: null/17008
Our complete environment is:
Java VM:
--------------------------
java version "1.5.0_24"
Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_24-b02
20100703 solaris sparc (SR12))
Java HotSpot(TM) Server VM (build 1.5.0_24-b02, mixed mode)
IBM Java ORB build orb50-20100629
XML build XSLT4J Java 2.7.19
XML build IBM JAXP 1.3.11
XML build XML4J 4.4.19
Database:
---------------------------
- Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bit
Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining
options
App Server:
---------------------------
Websphere ist Version 6.1.0.33.
JDBC driver:
---------------------------
ojdbc4.jar (10.1.0.4.0) for Java 1.4
Anybody an idea? I stick with that exception. I have already googled for
the specific error code or stack but I didn`t find anything. Any help is
appreciated!
Best regards
Sascha