Re: Infinite loop

Looks like index would need to be reindex. It would be better to contact Adobe Support as closer analysis would be required Chetan Mehrotra On Thu, Sep 15, 2016 at 6:32 PM, Thiago Sanches wrote: > I removed the index folder but the error persists. I tried to remove the >

Re: Oak HTTP binding README -> Error 500 OakConstraint0055

Hi Joe, > -> http -j -b localhost:8080/test jcr\\:primaryType=oak:Unstructured foo=abc > bar:=123 While I'm not completely sure of the whole type validation machinery (or auto-generation) etc. But doing this: ``` diff --git

Oak HTTP binding README -> Error 500 OakConstraint0055

Hi, I’m encountering a 500 Error when following the README.md on github at https://github.com/apache/jackrabbit-oak/blob/trunk/oak-http/README.md. I’m just getting into it and feel that I’m missing something obvious. Steps to reproduce: 1. Cloned the repository and created an IntelliJ

Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.12

[X] +1 Approve the release alex On Thu, Sep 15, 2016 at 6:49 PM, Francesco Mari wrote: > +1 > > 2016-09-15 18:29 GMT+02:00 Michael Dürig : > > Hi, > > > > We solved 36 issues in this release: > >

Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.12

+1 2016-09-15 18:29 GMT+02:00 Michael Dürig : > Hi, > > We solved 36 issues in this release: > https://issues.apache.org/jira/browse/OAK/fixforversion/12338153 > > There are still some outstanding issues: > https://issues.apache.org/jira/browse/OAK/component/12329487 > >

Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.12

On 15.9.16 6:29 , Michael Dürig wrote: [X] +1 Approve the release Michael

[VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.12

Hi, We solved 36 issues in this release: https://issues.apache.org/jira/browse/OAK/fixforversion/12338153 There are still some outstanding issues: https://issues.apache.org/jira/browse/OAK/component/12329487 Staging repository:

Oak Segment Tar 0.0.12 release plan

Hi, I would like to cut the Oak Segment Tar 0.0.12 release as we already have 36 issues fixed for 0.0.12. If there is no objections I would move the 6 unresolved issues to 0.0.14. I'm going to start the process right now, sorry for the short notice. If there are justified objections there

Faster reference binary handling

Hi all, while working with Oak S3 DS I have witnessed slowness (no numbers, just 'slow' from a user perspective) in persisting a binary using its reference; although this may be related to some environment specific issue I wondered about the reference binary handling we introduced in JCR-3534

Re: Infinite loop

I removed the index folder but the error persists. I tried to remove the "/crx/packmgr/service.jsp/file" node (that was causing the error before) But still failing... 15.09.2016 12:58:31.417 *DEBUG* [pool-7-thread-3] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate [async] The index

Re: Infinite loop

Hello Chetan, good morning. Yes, there is a lot of ".bak" inside segmentstore folder with the creation time close to the "force" restart. I'll try to remove the index folder. Thanks for your help. On Thu, Sep 15, 2016 at 1:44 AM, Chetan Mehrotra wrote: > On Thu, Sep

Re: Infinite loop

Hello Vikas, good morning. *Just to confirm: does the drive which contains folderhave sufficient space now? Any chance that AEM process can't write to/repository/index/* folders?* Yes, because the related problem with the repository growing too fast. On Wed, Sep 14, 2016 at 6:03 PM, Vikas

Re: Minimum JDK version for 1.4

On 2016-09-14 15:40, Davide Giannella wrote: On 14/09/2016 12:27, Julian Reschke wrote: should we consider allowing JDK7 features in 1.4 as well? I'm perfectly fine with it. It looks like no one noticed the error and it's relatively low risk for 1.4. JD7 has been around for a while now. I

Re: IndexEditorProvider behaviour question.

Hi, Thanks for looking at this, sounds like you are on the case already. if I see anything else I'll let you know. Best Regards Ian On 15 September 2016 at 05:33, Chetan Mehrotra wrote: > Note that so far LuceneIndexEditor was used only for async indexing > case and