[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 778 - Still Failing
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #778) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/778/ to view the results. Changes: [mreutegg] OAK-4085: Malformed node type definition when reregistered after upgrade [frm] OAK-4089 - Don't start the observation susbsystem when starting the [reschke] OAK-4094: RDBDocumentStore: upgrade PostgreSQL JDBC driver dependency to Test results: 3 tests failed. FAILED: org.apache.jackrabbit.oak.standalone.RepositoryBootIT.repositoryLogin Error Message: Failed to load ApplicationContext Stack Trace: java.lang.IllegalStateException: Failed to load ApplicationContext at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:124) at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83) at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:117) at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:83) at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:228) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:230) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:249) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:89) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:193) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) 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:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Caused by: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859) at java.util.ArrayList$Itr.next(ArrayList.java:831) at ch.qos.logback.classic.Logger.recursiveReset(Logger.java:344) at ch.qos.logback.classic.Logger.recursiveReset(Logger.java:345) at ch.qos.logback.classic.LoggerContext.reset(LoggerContext.java:213) at org.springframework.boot.logging.logback.LogbackLoggingSystem.reinitialize(LogbackLoggingSystem.java:195) at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithConventions(AbstractLoggingSystem.java:64) at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:49) at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:106) at org.springframework.boot.l
Re: [VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)
Hi, On Mon, Mar 7, 2016 at 4:21 PM, Davide Giannella wrote: > Please vote on releasing this package as Apache Jackrabbit Oak 1.4.0. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > +1 Release this package as Apache Jackrabbit Oak 1.4.0 Thanks Amit
Re: [VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)
[X] +1 Release this package as Apache Jackrabbit Oak 1.4.0 Regards Julian On Mon, Mar 7, 2016 at 11:51 AM, Davide Giannella wrote: > A candidate for the Jackrabbit Oak 1.4.0 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.4.0/ > > The release candidate is a zip archive of the sources in: > > > https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.4.0/ > > The SHA1 checksum of the archive is > 483493eacea4c64a6a568982058996d745ad4e18. > > A staged Maven repository is available for review at: > > https://repository.apache.org/ > > The command for running automated checks against this release candidate is: > > $ sh check-release.sh oak 1.4.0 483493eacea4c64a6a568982058996d745ad4e18 > > Please vote on releasing this package as Apache Jackrabbit Oak 1.4.0. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit Oak 1.4.0 > [ ] -1 Do not release this package because... > > Davide >
R: R: R: Critical questions about OAK
Hi,
sorry if i continue to ask you about these critical questions but we'd like to
build on OAK a platform that manage over 200M of documents so we'd like to know
in deep how OAK works.
Query Engine
1. I didn't understand how Traverse recovers phisically the graph to
traverse. Is provided in memory ? does it make a search on filesystem or db to
obtain a correct portion of graph and then traverse it ?
2. Can you point out the Traverse classes ? Or unit test?
Instead for RDBMS question i noticed that with our simple class, the first time
i add the node. The second time we obtain an error loading RepositoryImpl.
In detail when MutableTree try to make beforewrite, throw an illegalstate
exception ("this tree does not exist")
Thanks in advance,
best regards
-Messaggio originale-
Da: Julian Reschke [mailto:julian.resc...@gmx.de]
Inviato: venerdì 4 marzo 2016 08:09
A: oak-dev@jackrabbit.apache.org
Oggetto: Re: R: R: Critical questions about OAK
On 2016-03-03 15:48, Ancona Francesco wrote:
> Yes but i'm asking if there is a way or a configuration to call rdbms using
> jcrrepository like oak examples in getting start.
>
> final DocumentMK.Builder builder = new DocumentMK.Builder();
> builder.setBlobStore(createFileSystemBlobStore());
> final DocumentNodeStore ns = getRDBDocumentNodeStore(builder);
> Oak oak = new Oak(ns);
> Jcr jcr = new Jcr(oak);
>
> Repository repo = jcr.createRepository();
>
> Thanks.
It looks like some RepositoryInitializer is missing (AFAIU, it would take care
of creating the initial content).
Best regards, Julian
This footnote confirms that this email message has been scanned by PineApp
Mail-SeCure for the presence of malicious code, vandals & computer viruses.
Re: [VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)
[X] +1 Release this package as Apache Jackrabbit Oak 1.4.0 Davide
Re: [VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)
Hi, On 07/03/16 11:51, "Davide Giannella" wrote: >Please vote on releasing this package as Apache Jackrabbit Oak 1.4.0. >The vote is open for the next 72 hours and passes if a majority of at >least three +1 Jackrabbit PMC votes are cast. All checks OK. +1 Release this package as Apache Jackrabbit Oak 1.4.0 Regards Marcel
Re: [VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)
On 2016-03-07 11:51, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.4.0 Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)
On Mon, Mar 7, 2016 at 11:51 AM, Davide Giannella wrote: > ... [X] +1 Release this package as Apache Jackrabbit Oak 1.4.0
[VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)
A candidate for the Jackrabbit Oak 1.4.0 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.4.0/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.4.0/ The SHA1 checksum of the archive is 483493eacea4c64a6a568982058996d745ad4e18. A staged Maven repository is available for review at: https://repository.apache.org/ The command for running automated checks against this release candidate is: $ sh check-release.sh oak 1.4.0 483493eacea4c64a6a568982058996d745ad4e18 Please vote on releasing this package as Apache Jackrabbit Oak 1.4.0. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. [ ] +1 Release this package as Apache Jackrabbit Oak 1.4.0 [ ] -1 Do not release this package because... Davide
[RESULT][VOTE] Release Apache Jackrabbit Oak 1.4.0
Hello Team, the vote passes as follows: +1 Alex Parvulescu -1 Amit Jain -1 Davide Giannella -1 Julian Reschke -1 Marcel Reutegger -1 Tommaso Teofili Thanks for voting. I'll cancel this one. -- Davide
Re: oak-resilience
Cool stuff Tomek! This was something which was discussed in last Oakathon so great to have a way to do resilience testing programatically. Would give it a try Chetan Mehrotra On Mon, Mar 7, 2016 at 1:49 PM, Stefan Egli wrote: > Hi Tomek, > > Would also be interesting to see the effect on the leases and thus > discovery-lite under high memory load and network problems. > > Cheers, > Stefan > > On 04/03/16 11:13, "Tomek Rekawek" wrote: > >>Hello, >> >>For some time I've worked on a little project called oak-resilience. It >>aims to be a resilience testing framework for the Oak. It uses >>virtualisation to run Java code in a controlled environment, that can be >>spoilt in different ways, by: >> >>* resetting the machine, >>* filling the JVM memory, >>* filling the disk, >>* breaking or deteriorating the network. >> >>I described currently supported features in the README file [1]. >> >>Now, once I have a hammer I'm looking for a nail. Could you share your >>thoughts on areas/features in Oak which may benefit from being >>systematically tested for the resilience in the way described above? >> >>Best regards, >>Tomek >> >>[1] >>https://github.com/trekawek/jackrabbit-oak/tree/resilience/oak-resilience >> >>-- >>Tomek Rękawek | Adobe Research | www.adobe.com >>reka...@adobe.com >> > >
Re: oak-resilience
Hi Tomek, Would also be interesting to see the effect on the leases and thus discovery-lite under high memory load and network problems. Cheers, Stefan On 04/03/16 11:13, "Tomek Rekawek" wrote: >Hello, > >For some time I've worked on a little project called oak-resilience. It >aims to be a resilience testing framework for the Oak. It uses >virtualisation to run Java code in a controlled environment, that can be >spoilt in different ways, by: > >* resetting the machine, >* filling the JVM memory, >* filling the disk, >* breaking or deteriorating the network. > >I described currently supported features in the README file [1]. > >Now, once I have a hammer I'm looking for a nail. Could you share your >thoughts on areas/features in Oak which may benefit from being >systematically tested for the resilience in the way described above? > >Best regards, >Tomek > >[1] >https://github.com/trekawek/jackrabbit-oak/tree/resilience/oak-resilience > >-- >Tomek Rękawek | Adobe Research | www.adobe.com >reka...@adobe.com >
Re: oak-resilience
On 4.3.16 11:13 , Tomek Rekawek wrote: Hello, For some time I've worked on a little project called oak-resilience. It aims to be a resilience testing framework for the Oak. It uses virtualisation to run Java code in a controlled environment, that can be spoilt in different ways, by: * resetting the machine, * filling the JVM memory, * filling the disk, * breaking or deteriorating the network. I described currently supported features in the README file [1]. Now, once I have a hammer I’m looking for a nail. Could you share your thoughts on areas/features in Oak which may benefit from being systematically tested for the resilience in the way described above? See https://issues.apache.org/jira/browse/OAK-1844 and https://wiki.apache.org/jackrabbit/Resilience for some initial groundwork. Great to have some tooling now! Michael
Re: oak-resilience
Hi Tomek, from a DocumentNodeStore point of view the first and the last item would be interesting. We do have tests that check the recovery logic, but we still lack integration tests on a higher level with multiple cluster nodes joining, leaving and crashing. the impact of network issues is IMO an even bigger topic, specifically for the MongoDB backend. There it is not just the behaviour of Oak that needs to be tested but also in conjunction with how MongoDB behaves when the network turns bad. Regards Marcel On 04/03/16 11:13, "Tomek Rekawek" wrote: >Hello, > >For some time I've worked on a little project called oak-resilience. It >aims to be a resilience testing framework for the Oak. It uses >virtualisation to run Java code in a controlled environment, that can be >spoilt in different ways, by: > >* resetting the machine, >* filling the JVM memory, >* filling the disk, >* breaking or deteriorating the network. > >I described currently supported features in the README file [1]. > >Now, once I have a hammer I'm looking for a nail. Could you share your >thoughts on areas/features in Oak which may benefit from being >systematically tested for the resilience in the way described above? > >Best regards, >Tomek > >[1] >https://github.com/trekawek/jackrabbit-oak/tree/resilience/oak-resilience > >-- >Tomek Rękawek | Adobe Research | www.adobe.com >reka...@adobe.com >
