jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8152) RDB*Store: ConcurrentAddIT fails for Oracle
Date Wed, 20 Mar 2019 16:29:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797324#comment-16797324
] 

Julian Reschke commented on OAK-8152:
-------------------------------------

See also https://docs.oracle.com/cd/B28359_01/appdev.111/b28393/adlob_tables.htm#CIHEHGCH

> RDB*Store: ConcurrentAddIT fails for Oracle
> -------------------------------------------
>
>                 Key: OAK-8152
>                 URL: https://issues.apache.org/jira/browse/OAK-8152
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: rdbmk
>            Reporter: Julian Reschke
>            Priority: Major
>
> {noformat}
> [ERROR] addNodesSameParent[DocumentNodeStore[RDB] on jdbc:oracle:thin:@localhost:1521:orcl](org.apache.jackrabbit.oak.jcr.ConcurrentAddIT)
 Time elapsed: 106.515 s  <<< FAILURE!
> java.lang.AssertionError: javax.jcr.RepositoryException: OakOak0001: Failed to load document
with 1:/test
>         at org.apache.jackrabbit.oak.jcr.ConcurrentAddIT.addNodesSameParent(ConcurrentAddIT.java:102)
> {noformat}
> Underlying reason seems to be:
> {noformat}
> Caused by: java.sql.SQLException: ORA-01555: Snapshot zu alt: Rollback-Segmentnummer
 namens "" ist zu klein.
> ORA-22924: Snapshot zu alt
>         at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
>         at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:441)
>         at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:436)
>         at oracle.jdbc.driver.T4C8TTILob.processError(T4C8TTILob.java:758)
>         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
>         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
>         at oracle.jdbc.driver.T4C8TTILob.read(T4C8TTILob.java:146)
>         at oracle.jdbc.driver.T4CConnection.getBytes(T4CConnection.java:3027)
>         at oracle.sql.BLOB.getBytes(BLOB.java:340)
>         at oracle.sql.BLOB.getBytes(BLOB.java:222)
>         at oracle.jdbc.driver.T4CBlobAccessor.getBytes(T4CBlobAccessor.java:202)
>         at oracle.jdbc.driver.GeneratedStatement.getBytes(GeneratedStatement.java:143)
>         at oracle.jdbc.driver.GeneratedScrollableResultSet.getBytes(GeneratedScrollableResultSet.java:164)
>         at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:498)
>         at org.apache.tomcat.jdbc.pool.interceptor.StatementDecoratorInterceptor$ResultSetProxy.invoke(StatementDecoratorInterceptor.java:286)
>         at com.sun.proxy.$Proxy39.getBytes(Unknown Source)
>         at org.apache.jackrabbit.oak.plugins.document.rdb.RDBDocumentStoreJDBC.read(RDBDocumentStoreJDBC.java:858)
> {noformat}
> ...that is, the BDATA blob is not available anymore. Seems to be a problem related to
the retention of blobs. Need to find out whether this is purely an admin issue or whether
we need a code change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message