On Sat, Jul 30, 2011 at 11:23 PM, John cyuczieekc <cyuczie...@gmail.com>wrote:
> I did a quick check of what you said
> org.neo4j.index.bdbje.BerkeleyDbCommand.writeToFile(LogBuffer)
> char[] indexName = indexId.indexName.toCharArray();
> buffer.putInt( indexName.length );
> buffer.put( indexName );
>
> I'm probably missing something but on my side it looks like it writes
> length then indexName (and I didn't update from github, just in case you've
> already fixed this)
>
> Either way, my impression of what was happening is that some files got
> deleted, except some ie. the log, which were still open/in use, and maybe
> when recovery was tried, either it couldn't be opened, or due to being
> opened contained impartial data, or all was well but recovery couldn't
> happen because the log needed some other files or a previous database
> snapshot upon which to apply the recovered transactions
>
> I only get that messages.log being unable to delete when I allow the test
> testFindCreatedIndex() to run, I cannot yet figure out who creates that file
> and to make sure it's being closed
>
> correction testInsertionSpeed()
> John.
>
>
> On Sat, Jul 30, 2011 at 11:09 PM, Niels Hoogeveen <
> pd_aficion...@hotmail.com> wrote:
>
>>
>> The problem is indeed related to not properly closing the bdb database,
>> and that is triggers another problem. In BerkeleyDbCommand data is being
>> stored into the transaction log and been read from the transaction log later
>> on. Something goes wrong making the indexName being retrieved from the
>> transaction log look like garbage.
>> I think I have located the problem. In the method
>> BerkeleyDbCommand#writeToFile the sequence of elements written to the buffer
>> is different from the order in which the method
>> BerkeleyDbCommand#readCommand reads those elements. The
>> BerkeleyDbCommand#writeToFile method cannot be correct, because it first
>> writes the indexName and then its length. It should of course first write
>> the length and then the indexName.
>> Niels
>> > Date: Sat, 30 Jul 2011 22:51:40 +0200
>> > From: cyuczie...@gmail.com
>> > To: user@lists.neo4j.org
>> > Subject: Re: [Neo4j] bdb-index
>> >
>> > found out that I don't need to call index.delete() all the time, instead
>> > BerkeleyDbDataSource.close() aka XaDataSource.close() should do what
>> > index.delete() does, namely closing all databases (related to this
>> > datasource) and their bdb environment; so I do just that.
>> >
>> > Therefore I answer some parts I asked before.
>> >
>> > And that logical.log.1 seems to be a part of XA Transactions and I must
>> find
>> > a way to see that it's closed or something
>> >
>> > On Sat, Jul 30, 2011 at 10:15 PM, John cyuczieekc <cyuczie...@gmail.com
>> >wrote:
>> >
>> > > in TestBerkeley.java
>> > > So far I've found that, bdb environment(and relevant databases)
>> is(are)
>> > > only closed when index.delete() is called
>> > > and that can only be called when the current transaction is finished
>> (else
>> > > it will complain that some bdb databases are not opened on txn commit)
>> > > Applying all those changes, the following file is still in use (due
>> to
>> > > cannot be deleted):
>> > >
>> > > E:\wrkspc\bdb-index-fork\target\var\neo4j-db\logical.log.1
>> > > This seems to be part of neo4j, though I am not sure why would it
>> still be
>> > > in use even after graphDb.shutdown()
>> > > Any ideas why that would be still in use? Is graphDb.shutdown()
>> blocking
>> > > until everything is closed? or are there still threads left keeping
>> files
>> > > locked? or shutdown is delegated to other threads which may still be
>> doing
>> > > their work when .shutdown() returns ?
>> > >
>> > > By looking at some testcases in neo4j, I see that *index.delete() can
>> be
>> > > called before transaction finished, is this correct* ? anyone?
>> > > ie.
>> > > beginTx();
>> > > index = graphDb.index().forNodes( INDEX_NAME );
>> > > index.delete();
>> > > restartTx();
>> > > where
>> > > void restartTx()
>> > > {
>> > > finishTx( true );
>> > > beginTx();
>> > > }
>> > >
>> > > in this case, if that's true that index.delete() should not cause the
>> txn
>> > > commit to fail, then this needs to be fixed in bdb-index
>> > >
>> > > Also,* is neo4j closing the indexes* somehow when graphDb.shutdown() ?
>> it
>> > > seems to me the only close would be index.delete() and neo4j isn't
>> closing
>> > > them, thus leaving the bdb Environment still open, thus tests that
>> require
>> > > shutdown and reopen of graphdb will fail since bdb wasn't itself
>> shutdown
>> > > and reopened but was left still open.
>> > > Maybe closing the indexes is left to the user then? it's fine with me,
>> just
>> > > so long as I know
>> > >
>> > >
>> > > disorganized John :)
>> > >
>> > >
>> > > On Sat, Jul 30, 2011 at 9:06 PM, John cyuczieekc <
>> cyuczie...@gmail.com>wrote:
>> > >
>> > >> looks like before delving too deep, I found that attempting to
>> deleting
>> > >> the dbPath ie. deleteFileOrDirectory( dbPath );
>> > >> fails, right after graphDB.shutdown(); - I'm excluding the
>> possibility
>> > >> that that method is deferring the shutdown to another thread and thus
>> is
>> > >> non-blocking (due to my timing of it from previous tests looks like
>> it takes
>> > >> at most 3 sec)
>> > >>
>> > >> ie. this file cannot be deleted (likely's already in use):
>> > >>
>> E:\wrkspc\bdb-index-fork\target\var\neo4j-db\index\bdb\Node\fast\name\je.info.0
>> > >> I need to check if and how bdb gets shutdown also, it kind of looks
>> like
>> > >> it doesn't
>> > >> So since that file doesn't get deleted, but probably others do, maybe
>> that
>> > >> is why we get those weird errors:
>> > >>
>> > >> Jul 30, 2011 9:04:11 PM
>> > >> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog
>> > >> doInternalRecovery
>> > >> INFO: Non clean shutdown detected on log
>> > >> [E:\wrkspc\bdb-index-fork\target\var\neo4j-db/logical.log.1].
>> Recovery
>> > >> started ...
>> > >> java.lang.RuntimeException:
>> com.sleepycat.je.EnvironmentFailureException:
>> > >> (JE 4.1.10) Problem creating output files in:
>> > >> E:\wrkspc\bdb-index-fork\target\var\neo4j-db\index\bdb\Node\
>> \name/
>> > >> je.info UNEXPECTED_EXCEPTION: Unexpected internal Exception, may
>> have
>> > >> side effects.
>> > >> at
>> > >>
>> org.neo4j.index.bdbje.BerkeleyDbDataSource.createDB(BerkeleyDbDataSource.java:377)
>> > >> at
>> > >>
>> org.neo4j.index.bdbje.BerkeleyDbDataSource.getDatabase(BerkeleyDbDataSource.java:278)
>> > >> at
>> > >>
>> org.neo4j.index.bdbje.BerkeleydbTransaction.doCommit(BerkeleyDbTransaction.java:191)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransaction.java:319)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.injectOnePhaseCommit(XaResourceManager.java:366)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog.applyOnePhaseCommitEntry(XaLogicalLog.java:514)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog.applyEntry(XaLogicalLog.java:445)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog.doInternalRecovery(XaLogicalLog.java:768)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog.open(XaLogicalLog.java:253)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog.open(XaLogicalLog.java:134)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.xaframework.XaContainer.openLogicalLog(XaContainer.java:97)
>> > >> at
>> > >>
>> org.neo4j.index.bdbje.BerkeleyDbDataSource.<init>(BerkeleyDbDataSource.java:96)
>> > >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> > >> Method)
>> > >> at
>> > >>
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> > >> at
>> > >>
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> > >> at
>> java.lang.reflect.Constructor.newInstance(Constructor.java:525)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.XaDataSourceManager.create(XaDataSourceManager.java:76)
>> > >> at
>> > >>
>> org.neo4j.kernel.impl.transaction.TxModule.registerDataSource(TxModule.java:175)
>> > >> at
>> > >>
>> org.neo4j.index.bdbje.BerkeleyDbIndexImplementation.<init>(BerkeleyDbIndexImplementation.java:67)
>> > >> at
>> > >>
>> org.neo4j.index.bdbje.BerkeleyDbIndexImplementation.<init>(BerkeleyDbIndexImplementation.java:58)
>> > >> at
>> > >>
>> org.neo4j.index.bdbje.BerkeleyDbIndexProvider.load(BerkeleyDbIndexProvider.java:38)
>> > >> at
>> > >>
>> org.neo4j.kernel.KernelData.loadIndexImplementations(KernelData.java:146)
>> > >> at
>> > >>
>> org.neo4j.kernel.EmbeddedGraphDbImpl$2.initializeIndexProviders(EmbeddedGraphDbImpl.java:179)
>> > >> at
>> org.neo4j.kernel.GraphDbInstance.start(GraphDbInstance.java:159)
>> > >> at
>> > >>
>> org.neo4j.kernel.EmbeddedGraphDbImpl.<init>(EmbeddedGraphDbImpl.java:189)
>> > >> at
>> > >>
>> org.neo4j.kernel.EmbeddedGraphDatabase.<init>(EmbeddedGraphDatabase.java:86)
>> > >> at
>> > >>
>> org.neo4j.kernel.EmbeddedGraphDatabase.<init>(EmbeddedGraphDatabase.java:63)
>> > >> at
>> org.neo4j.index.bdbje.Neo4jTestCase.setUpDb(Neo4jTestCase.java:54)
>> > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > >> at
>> > >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> > >> at
>> > >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> > >> at java.lang.reflect.Method.invoke(Method.java:601)
>> > >> at
>> > >>
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>> > >> at
>> > >>
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>> > >> at
>> > >>
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>> > >> at
>> > >>
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
>> > >> at
>> > >>
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>> > >> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>> > >> at org.junit.runners.Suite.runChild(Suite.java:128)
>> > >> at org.junit.runners.Suite.runChild(Suite.java:24)
>> > >> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>> > >> at
>> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>> > >> at
>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>> > >> at
>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>> > >> at
>> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>> > >> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>> > >> at
>> > >>
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
>> > >> at
>> > >>
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>> > >> at
>> > >>
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
>> > >> at
>> > >>
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
>> > >> at
>> > >>
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
>> > >> at
>> > >>
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
>> > >> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE 4.1.10)
>> > >> Problem creating output files in:
>> > >> E:\wrkspc\bdb-index-fork\target\var\neo4j-db\index\bdb\Node\
>> > >>
>> > >>
>> > >> On Sat, Jul 30, 2011 at 8:22 PM, John cyuczieekc <
>> cyuczie...@gmail.com>wrote:
>> > >>
>> > >>> from my experience this kind of behaviour would happen mostly due to
>> > >>> using some static fields which are expected to be in initialized
>> state for
>> > >>> each test, or test class
>> > >>>
>> > >>> I also needed to mention that I get this error:
>> > >>> Jul 30, 2011 8:18:54 PM
>> > >>> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog
>> > >>> doInternalRecovery
>> > >>> INFO: Non clean shutdown detected on log
>> > >>> [E:\wrkspc\bdb-index-fork\target\var\batch/logical.log.1]. Recovery
>> started
>> > >>> ...
>> > >>> when running TestBerkeleyBatchInsert.java (all 3 tests in it) but
>> not
>> > >>> when running only the test in which it appears namely the method
>> > >>> testFindCreatedIndex()
>> > >>>
>> > >>> some state is carried from the previous tests, even if this is just
>> the
>> > >>> database not being deleted
>> > >>>
>> > >>> I'll check some more, ofc
>> > >>>
>> > >>>
>> > >>> On Sat, Jul 30, 2011 at 7:57 PM, John cyuczieekc <
>> cyuczie...@gmail.com>wrote:
>> > >>>
>> > >>>> (ignore these, skip to the bold part: ie. search BOLD)
>> > >>>> Thanks Niels, I just tried what you said, with maven 3.0.3 it
>> seemed to
>> > >>>> do some downloading work for a while then eventually got this:
>> > >>>> [ERROR] Failed to execute goal on project
>> neo4j-berkeleydb-je-index:
>> > >>>> Could not resolve dependencies for project
>> > >>>> org.neo4j:neo4j-berkeleydb-je-index:jar:0.1-SNAPSHOT: Could not
>> find
>> > >>>> artifact org.neo4j:neo4j-kernel:jar:1.3-SNAPSHOT in oracleReleases
>> (
>> > >>>> http://download.oracle.com/maven) -> [Help 1]
>> > >>>> I'll try to view/edit that pom maybe I need 1.4
>> > >>>> That seems to have worked, but now I get this:
>> > >>>> [INFO] Checking licenses...
>> > >>>> [INFO] Missing header in:
>> > >>>> e:\down\13th-floor-bdb-index-fb11e38\13th-floor-bdb-in
>> > >>>> dex-fb11e38\src\test\java\org\neo4j\index\bdbje\RawBDBSpeed.java
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] BUILD FAILURE
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] Total time: 1:10.949s
>> > >>>> [INFO] Finished at: Sat Jul 30 19:11:16 CEST 2011
>> > >>>> [INFO] Final Memory: 10M/156M
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [ERROR] Failed to execute goal
>> > >>>> com.mycila.maven-license-plugin:maven-license-plu
>> > >>>> gin:1.9.0:check (check-licenses) on project
>> neo4j-berkeleydb-je-index:
>> > >>>> Some file
>> > >>>> s do not have the expected license header -> [Help 1]
>> > >>>>
>> > >>>> How were you able to run mvn install ? did you have a different
>> config
>> > >>>> ie. auto ignore licenses? what about the 1.3 to 1.4 transformation,
>> did you
>> > >>>> have to manually do it? So far, using maven is more of a pain than
>> using
>> > >>>> simply eclipse and adding dependencies manually heh
>> > >>>>
>> > >>>> Maybe I should try maven 2, let's see...
>> > >>>> mvn -version
>> > >>>> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
>> > >>>> Java version: 1.6.0_26
>> > >>>> Java home: C:\Program Files\Java\jdk1.6.0_26\jre
>> > >>>> Default locale: en_US, platform encoding: Cp1252
>> > >>>> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>> > >>>>
>> > >>>> With original pom with 1.3 neo4j requirement I still got error,
>> changed
>> > >>>> to 1.4
>> > >>>> then works but I get the licenses issue again:
>> > >>>> [INFO] [enforcer:enforce {execution: enforce-maven}]
>> > >>>> [INFO] [license:check {execution: check-licenses}]
>> > >>>> [INFO] Checking licenses...
>> > >>>> [INFO] Missing header in:
>> > >>>> e:\down\13th-floor-bdb-index-fb11e38\13th-floor-bdb-in
>> > >>>> dex-fb11e38\src\test\java\org\neo4j\index\bdbje\RawBDBSpeed.java
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [ERROR] BUILD ERROR
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] Some files do not have the expected license header
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] For more information, run Maven with the -e switch
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] Total time: 23 seconds
>> > >>>> [INFO] Finished at: Sat Jul 30 19:19:23 CEST 2011
>> > >>>> [INFO] Final Memory: 34M/350M
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>>
>> > >>>> ok then, trying to fix the license for that file...
>> > >>>> also I've seen that it now work from eclipse when on pom.xml Run
>> > >>>> As->Maven install
>> > >>>> [INFO] Checking licenses...
>> > >>>> [INFO] Missing header in:
>> > >>>> E:\wrkspc\bdb-index-fork\src\test\java\AllTests.java
>> > >>>> [INFO] Missing header in:
>> > >>>>
>> E:\wrkspc\bdb-index-fork\src\test\java\org\neo4j\index\bdbje\RawBDBSpeed.java
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] BUILD FAILURE
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] Total time: 1.578s
>> > >>>> [INFO] Finished at: Sat Jul 30 19:25:02 CEST 2011
>> > >>>> [INFO] Final Memory: 16M/154M
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [ERROR] Failed to execute goal
>> > >>>> com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check
>> > >>>> (check-licenses) on project neo4j-berkeleydb-je-index: Some file
>> > >>>> s do not have the expected license header -> [Help 1]
>> > >>>>
>> > >>>> Ok after fixing the licenses for those 2 files, running from
>> eclipse
>> > >>>> yields:
>> > >>>>
>> > >>>> [INFO] Scanning for projects...
>> > >>>> [INFO]
>> > >>>>
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] Building neo4j-berkeleydb-je-index 0.1-SNAPSHOT
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO]
>> > >>>> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven)
>> @
>> > >>>> neo4j-berkeleydb-je-index ---
>> > >>>> [INFO]
>> > >>>> [INFO] --- maven-license-plugin:1.9.0:check (check-licenses) @
>> > >>>> neo4j-berkeleydb-je-index ---
>> > >>>> [INFO] Checking licenses...
>> > >>>> [INFO]
>> > >>>> [INFO] --- maven-resources-plugin:2.4.3:resources
>> (default-resources) @
>> > >>>> neo4j-berkeleydb-je-index ---
>> > >>>> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.6
>> is
>> > >>>> missing, no dependency information available
>> > >>>> [WARNING] The POM for org.apache.maven:maven-project:jar:2.0.6 is
>> > >>>> missing, no dependency information available
>> > >>>> [WARNING] The POM for org.apache.maven:maven-core:jar:2.0.6 is
>> missing,
>> > >>>> no dependency information available
>> > >>>> [WARNING] The POM for org.apache.maven:maven-artifact:jar:2.0.6 is
>> > >>>> missing, no dependency information available
>> > >>>> [WARNING] The POM for org.apache.maven:maven-settings:jar:2.0.6 is
>> > >>>> missing, no dependency information available
>> > >>>> [WARNING] The POM for org.apache.maven:maven-model:jar:2.0.6 is
>> missing,
>> > >>>> no dependency information available
>> > >>>> [WARNING] The POM for org.apache.maven:maven-monitor:jar:2.0.6 is
>> > >>>> missing, no dependency information available
>> > >>>> [WARNING] The POM for
>> > >>>> org.apache.maven.shared:maven-filtering:jar:1.0-beta-4 is missing,
>> no
>> > >>>> dependency information available
>> > >>>> [WARNING] The POM for
>> org.codehaus.plexus:plexus-interpolation:jar:1.13
>> > >>>> is missing, no dependency information available
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] BUILD FAILURE
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [INFO] Total time: 1.780s
>> > >>>> [INFO] Finished at: Sat Jul 30 19:32:06 CEST 2011
>> > >>>> [INFO] Final Memory: 16M/154M
>> > >>>> [INFO]
>> > >>>>
>> ------------------------------------------------------------------------
>> > >>>> [ERROR] Failed to execute goal
>> > >>>> org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources
>> > >>>> (default-resources) on project neo4j-berkeleydb-je-index: Executi
>> > >>>> on default-resources of goal
>> > >>>> org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources
>> failed:
>> > >>>> Plugin org.apache.maven.plugins:maven-resources-plugin:2.4.
>> > >>>> 3 or one of its dependencies could not be resolved: The following
>> > >>>> artifacts could not be resolved:
>> > >>>> org.apache.maven.shared:maven-filtering:jar:1.0-beta-4, org.c
>> > >>>> odehaus.plexus:plexus-interpolation:jar:1.13: The repository system
>> is
>> > >>>> offline but the artifact
>> > >>>> org.apache.maven.shared:maven-filtering:jar:1.0-beta-4 is not av
>> > >>>> ailable in the local repository. -> [Help 1]
>> > >>>> [ERROR]
>> > >>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>> with the
>> > >>>> -e switch.
>> > >>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>> > >>>> [ERROR]
>> > >>>> [ERROR] For more information about the errors and possible
>> solutions,
>> > >>>> please read the following articles:
>> > >>>> [ERROR] [Help 1]
>> > >>>>
>> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
>> > >>>>
>> > >>>> *BOLD *part :)
>> > >>>> Running from command line, but on a just now downloaded zip file(as
>> you
>> > >>>> said),
>> > >>>> it works (thus my eclipse maven still needs some work, ie. maybe
>> allow
>> > >>>> it internet access even though it's on ask in firewall)
>> > >>>> I mean I do see those errors that you said you're seeing... can't
>> really
>> > >>>> paste them here from terminal they will be broken with 80 chars per
>> line
>> > >>>>
>> > >>>> In eclipse without maven, running AllTests, although the tests do
>> pass,
>> > >>>> I failed to see that (possibly) the same exception(s) thrown by
>> maven
>> > >>>> install, are happening on console. But not when tests are run each
>> > >>>> individually. So, your errors happen both with mvn install and
>> AllTests
>> > >>>> (which runs them both one after the other, too). So that was a
>> failure to
>> > >>>> notice on my part :) that counting from 0 to 100 on console must've
>> moved up
>> > >>>> the exceptions and since tests were all success, I didn't scroll
>> up.
>> > >>>>
>> > >>>> Trying to fix,
>> > >>>>
>> > >>>>
>> > >>>>
>> > >>>> On Sat, Jul 30, 2011 at 3:28 PM, Niels Hoogeveen <
>> > >>>> pd_aficion...@hotmail.com> wrote:
>> > >>>>
>> > >>>>>
>> > >>>>> I use the download option on Github expand the zip in a directory
>> and
>> > >>>>> run mvn install in that directory without any problems.
>> > >>>>> Niels
>> > >>>>>
>> > >>>>> > Date: Sat, 30 Jul 2011 13:39:15 +0200
>> > >>>>> > From: cyuczie...@gmail.com
>> > >>>>> > To: user@lists.neo4j.org
>> > >>>>> > Subject: Re: [Neo4j] bdb-index
>> > >>>>> >
>> > >>>>> > "When running the mvn install, both tests are ran after
>> another."
>> > >>>>> > Since I didn't use mvn (xD) I ran the tests manually one by one,
>> but
>> > >>>>> what
>> > >>>>> > you say makes sense, it's likely the tests fail when ran one
>> after
>> > >>>>> the
>> > >>>>> > other, I'll see what happens with an @Suite
>> > >>>>> > since there are only 2 junit tests, with @Suite they work
>> > >>>>> > Let's see if I could run mvn install (btw, avoided mvn so far
>> because
>> > >>>>> I
>> > >>>>> > cannot install the git plugin for some reason and that other
>> error I
>> > >>>>> get)
>> > >>>>> > Looks like I still need to find out how to fix this error:
>> > >>>>> > [ERROR] The project
>> > >>>>> org.neo4j:neo4j-berkeleydb-je-index:0.1-SNAPSHOT
>> > >>>>> > (E:\wrkspc\bdb-index-fork\pom.xml) has 1 error
>> > >>>>> > [ERROR] Non-resolvable parent POM: The repository system is
>> > >>>>> offline but
>> > >>>>> > the artifact org.neo4j:parent-central:pom:18 is not available in
>> the
>> > >>>>> local
>> > >>>>> > repository. and 'parent.relativePath' points at wrong local POM
>> @
>> > >>>>> line 3,
>> > >>>>> > column 11 -> [Help 2]
>> > >>>>> >
>> > >>>>> > before I could do anything with maven...
>> > >>>>> > I'll skip trying to make maven to work for me for now, don't
>> feel
>> > >>>>> like it :)
>> > >>>>> >
>> > >>>>> > *I'm not qualified to fix this with maven, sorry*
>> > >>>>> > John
>> > >>>>> >
>> > >>>>> > On Fri, Jul 29, 2011 at 5:16 PM, Niels Hoogeveen
>> > >>>>> > <pd_aficion...@hotmail.com>wrote:
>> > >>>>> >
>> > >>>>> > >
>> > >>>>> > > Hi John,
>> > >>>>> > > Thanks for looking into this.
>> > >>>>> > > I am still seeing the same error I had before. When running
>> the mvn
>> > >>>>> > > install, both tests are ran after another. For some reason the
>> > >>>>> transaction
>> > >>>>> > > log sees an unclean shutdown and tries to commit pending
>> > >>>>> transactions.
>> > >>>>> > > During that process the index names of the bdb indexes are
>> being
>> > >>>>> retrieved
>> > >>>>> > > from binary storage. Here something goes wrong, because the
>> index
>> > >>>>> name
>> > >>>>> > > returned is garbage, so the recovery process fails because it
>> can't
>> > >>>>> find the
>> > >>>>> > > right index files.
>> > >>>>> > > Niels
>> > >>>>> > >
>> > >>>>> > > > Date: Fri, 29 Jul 2011 07:48:43 +0200
>> > >>>>> > > > From: cyuczie...@gmail.com
>> > >>>>> > > > To: user@lists.neo4j.org
>> > >>>>> > > > Subject: Re: [Neo4j] bdb-index
>> > >>>>> > > >
>> > >>>>> > > > I forked and "fixed", the tests are all working now:
>> > >>>>> > > > https://github.com/13th-floor/bdb-index
>> > >>>>> > > > Let me know if you want me to do a pull request, ... sadly I
>> > >>>>> applied
>> > >>>>> > > > formatting on RawBDBSpeed and the diff doesn't look pretty
>> if
>> > >>>>> you're
>> > >>>>> > > trying
>> > >>>>> > > > to see what changed
>> > >>>>> > > >
>> > >>>>> > > > John.
>> > >>>>> > > >
>> > >>>>> > > >
>> > >>>>> > > > On Thu, Jul 28, 2011 at 7:36 PM, Niels Hoogeveen
>> > >>>>> > > > <pd_aficion...@hotmail.com>wrote:
>> > >>>>> > > >
>> > >>>>> > > > >
>> > >>>>> > > > > Trying to find something useful to hide the implementation
>> book
>> > >>>>> keeping
>> > >>>>> > > of
>> > >>>>> > > > > Enhanced API, I tried out dbd-index as can be found here:
>> > >>>>> > > > > https://github.com/peterneubauer/bdb-index
>> > >>>>> > > > > It looks interesting, but fails its tests. When recovering
>> it
>> > >>>>> performs
>> > >>>>> > > > > BerkeleyDbCommand#readCommand from the log. The retrieved
>> > >>>>> indexName is
>> > >>>>> > > not
>> > >>>>> > > > > actually garbage. I would like to help make this component
>> > >>>>> workable,
>> > >>>>> > > but
>> > >>>>> > > > > area of the database is a bit beyond the scope that I
>> know.
>> > >>>>> > > > > I know this is completely unsupported software, but can
>> someone
>> > >>>>> give me
>> > >>>>> > > > > some pointers on how to fix this issue?
>> > >>>>> > > > > Niels
>> > >>>>> > > > > _______________________________________________
>> > >>>>> > > > > Neo4j mailing list
>> > >>>>> > > > > User@lists.neo4j.org
>> > >>>>> > > > > https://lists.neo4j.org/mailman/listinfo/user
>> > >>>>> > > > >
>> > >>>>> > > > _______________________________________________
>> > >>>>> > > > Neo4j mailing list
>> > >>>>> > > > User@lists.neo4j.org
>> > >>>>> > > > https://lists.neo4j.org/mailman/listinfo/user
>> > >>>>> > >
>> > >>>>> > > _______________________________________________
>> > >>>>> > > Neo4j mailing list
>> > >>>>> > > User@lists.neo4j.org
>> > >>>>> > > https://lists.neo4j.org/mailman/listinfo/user
>> > >>>>> > >
>> > >>>>> > _______________________________________________
>> > >>>>> > Neo4j mailing list
>> > >>>>> > User@lists.neo4j.org
>> > >>>>> > https://lists.neo4j.org/mailman/listinfo/user
>> > >>>>>
>> > >>>>> _______________________________________________
>> > >>>>> Neo4j mailing list
>> > >>>>> User@lists.neo4j.org
>> > >>>>> https://lists.neo4j.org/mailman/listinfo/user
>> > >>>>>
>> > >>>>
>> > >>>>
>> > >>>
>> > >>
>> > >
>> > _______________________________________________
>> > Neo4j mailing list
>> > User@lists.neo4j.org
>> > https://lists.neo4j.org/mailman/listinfo/user
>>
>> _______________________________________________
>> Neo4j mailing list
>> User@lists.neo4j.org
>> https://lists.neo4j.org/mailman/listinfo/user
>>
>
>
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
