Return-Path: 
 <dev-return-15051-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
Received: (qmail 1221 invoked from network); 13 Nov 2007 19:11:00 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 13 Nov 2007 19:11:00 -0000
Received: (qmail 99071 invoked by uid 500); 13 Nov 2007 19:10:46 -0000
Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
Received: (qmail 99045 invoked by uid 500); 13 Nov 2007 19:10:46 -0000
Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:dev@jackrabbit.apache.org>
List-Id: <dev.jackrabbit.apache.org>
Reply-To: dev@jackrabbit.apache.org
Delivered-To: mailing list dev@jackrabbit.apache.org
Received: (qmail 99036 invoked by uid 99); 13 Nov 2007 19:10:46 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2007 11:10:46 -0800
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of CBielen@comcastnets.com
 designates 208.78.120.142 as permitted sender)
Received: from [208.78.120.142] (HELO smtp02.comcastnets.com) (208.78.120.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2007 19:10:30 +0000
X-IronPort-AV: E=Sophos;i="4.21,411,1188802800";
   d="scan'208,217";a="78084"
Received: from unknown (HELO LA1-CNS-FE-52.CNS.COMCASTNETS.COM) ([10.7.1.38])
  by smtp02.comcastnets.com with ESMTP; 13 Nov 2007 11:10:47 -0800
Received: from LA-CNS-EXCH.CNS.COMCASTNETS.COM ([10.7.1.51]) by
 LA1-CNS-FE-52.CNS.COMCASTNETS.COM with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 13 Nov 2007 11:10:05 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C82628.CC8A2BE3"
Subject: Errors Rebuilding Indexes and Checking Consistency after Content
 Import.
Date: Tue, 13 Nov 2007 11:10:03 -0800
Message-ID: 
 <B07E9D0550FBCD438DF945950E8FC67E7968F1@LA-CNS-EXCH.CNS.COMCASTNETS.COM>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Errors Rebuilding Indexes and Checking Consistency after Content
 Import.
Thread-Index: AcgmKMupr79upyhCQ42EzGnQZFNnQQ==
From: "Colin Bielen" <CBielen@comcastnets.com>
To: <dev@jackrabbit.apache.org>
X-OriginalArrivalTime: 13 Nov 2007 19:10:05.0443 (UTC)
 FILETIME=[CCABFD30:01C82628]
X-Virus-Checked: Checked by ClamAV on apache.org

------_=_NextPart_001_01C82628.CC8A2BE3
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi group. I have an import/export related question/issue.=20

We've written a jackrabbit importer that does a node-by-node system view
export of approximately 200k content items from a source repository in
to a jboss-embedded Jackrabbit 1.3.3 repository using the Derby Bundle
PersistenceManager.

The import seems to run and complete OK, and the jackrabbit repository
appears to store/read/query imported content correctly across multiple
expected (and unexpected)  restarts.  However, when we delete the
content indexes (or even just set the PM "consistencyCheck" to "true")
we get the following nasty error followed by a failure to start up the
repository:

2007-11-09 20:25:41,836 ERROR
[org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManage
r] Error in bundle
ERROR XJ073: The data in this BLOB or CLOB is no longer available.  The
BLOB/CLOB's transaction may be committed, or its connection is closed.
	at
org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
	at org.apache.derby.impl.jdbc.EmbedBlob.<init>(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedResultSet.getBlob(Unknown
Source)
	at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.checkConsistency(BundleDbPersistenceManager.java:693)
	at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.init(BundleDbPersistenceManager.java:571)
	at
org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager.in
it(DerbyPersistenceManager.java:265)
	at
org.apache.jackrabbit.core.RepositoryImpl.createPersistenceManager(Repos
itoryImpl.java:1117)
	at
org.apache.jackrabbit.core.RepositoryImpl.access$600(RepositoryImpl.java
:99)
	at
org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.initialize(Repos
itoryImpl.java:1695)
	at
org.apache.jackrabbit.core.RepositoryImpl.initWorkspace(RepositoryImpl.j
ava:540)
	at
org.apache.jackrabbit.core.RepositoryImpl.initStartupWorkspaces(Reposito
ryImpl.java:379)
	at
org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:286
)
	at
org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:521
)
	at
org.apache.jackrabbit.jca.JCARepositoryManager$Reference.create(JCARepos
itoryManager.java:167)
	at
org.apache.jackrabbit.jca.JCARepositoryManager.createRepository(JCARepos
itoryManager.java:75)
	at
org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createRepository(J
CAManagedConnectionFactory.java:289)
	at
org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createConnectionFa
ctory(JCAManagedConnectionFactory.java:124)
	at
org.jboss.resource.connectionmanager.ConnectionFactoryBindingService.cre
ateConnectionFactory(ConnectionFactoryBindingService.java:128)
	at
org.jboss.resource.connectionmanager.ConnectionFactoryBindingService.sta
rtService(ConnectionFactoryBindingService.java:65)
	at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp
ort.java:289)
	at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
Support.java:245)
	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)

Has anyone else come accross this?  Our initial suspicion was some sort
of database corruption but when we comment out the  <SearchIndex>
declaration from the workspace.xml the repository starts up fine and all
the non-query related functions seem to work as expected.  We also did a
node walk of the entire repository to try and flush out any corrupt
nodes but couldn't find any and all the content appeared correct. =20

Any information or advice as to the cause or how to troubleshoot this
further would be greatly appreciated.=20

Thanks!

-Colin


P.S. Here are the persistence manager options we're using for the
workspace in question:=20

<PersistenceManager
class=3D"org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceMa=
n
ager">
           <param name=3D"url"
value=3D"jdbc:derby:${wsp.home}/db;create=3Dtrue"/>
           <param name=3D"schemaObjectPrefix" value=3D"${wsp.name}_"/>
           <param name=3D"consistencyCheck" value=3D"true"/>
           <param name=3D"consistencyFix" value=3D"true"/>
           <param name=3D"derbyStorageInitialPages" value=3D"16"/>
           <param name=3D"derbyStorageMinimumRecordSize" =
value=3D"1024"/>
           <param name=3D"derbyStoragePageCacheSize" value=3D"1024"/>
           <param name=3D"derbyStoragePageReservedSpace" value=3D"20"/>
           <param name=3D"derbyStoragePageSize" value=3D"16384"/>
</PersistenceManager>

------_=_NextPart_001_01C82628.CC8A2BE3--