Thank you! That fixed both the problem on initialisation and on writes
to my already converted repository!

On 29 July 2014 19:31, Chetan Mehrotra <[email protected]> wrote:
> Hi Torgeir,
>
>> Repository oakRepository = new Jcr(oak)
>>  .with(new InitialContent())
>>
>>  .with(JcrConflictHandler.JCR_CONFLICT_HANDLER)
>>  .with(new EditorHook(new VersionEditorProvider()))
>
> The Jcr constructor already registers a set of predefined editors and
> validators etc. So you should not be adding them again. Instead new
> Jcr(oak).createRepository(); should be sufficient unless you want to
> add extra editors which are not registered by default.
>
> Can you try with above mode?
>
> Chetan Mehrotra
>
>
> On Tue, Jul 29, 2014 at 2:23 PM, Torgeir Veimo <[email protected]> 
> wrote:
>> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
>> OakConstraint0030: Uniqueness constraint violated at path [/] for one
>> of the property in [rep:principalName] having value anonymous
>> at 
>> org.apache.jackrabbit.oak.plugins.index.property.PropertyIndexEditor.leave(PropertyIndexEditor.java:282)
>> at 
>> org.apache.jackrabbit.oak.spi.commit.CompositeEditor.leave(CompositeEditor.java:74)
>> at 
>> org.apache.jackrabbit.oak.spi.commit.CompositeEditor.leave(CompositeEditor.java:74)
>> at 
>> org.apache.jackrabbit.oak.spi.commit.EditorDiff.process(EditorDiff.java:56)
>> at 
>> org.apache.jackrabbit.oak.plugins.index.IndexUpdate.enter(IndexUpdate.java:121)
>> at 
>> org.apache.jackrabbit.oak.spi.commit.VisibleEditor.enter(VisibleEditor.java:57)
>> at 
>> org.apache.jackrabbit.oak.spi.commit.EditorDiff.process(EditorDiff.java:49)
>> at 
>> org.apache.jackrabbit.oak.spi.commit.EditorHook.processCommit(EditorHook.java:54)
>> at 
>> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStore$Commit.prepare(SegmentNodeStore.java:329)
>> at 
>> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStore$Commit.optimisticMerge(SegmentNodeStore.java:360)
>> at 
>> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStore$Commit.execute(SegmentNodeStore.java:416)
>> at 
>> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStore.merge(SegmentNodeStore.java:133)
>> at 
>> org.apache.jackrabbit.oak.spi.lifecycle.OakInitializer.initialize(OakInitializer.java:62)
>>
>>
>> On 29 July 2014 18:34, Torgeir Veimo <[email protected]> wrote:
>>> With trunk;
>>>
>>> 18:32:33,125 ERROR manager.SessionManager.afterPropertiesSet() - line
>>> 212 [] - unable to configure OAK repository;
>>>
>>> java.lang.RuntimeException:
>>> org.apache.jackrabbit.oak.api.CommitFailedException:
>>> OakConstraint0030: Uniqueness constraint violated at path [/] for one
>>> of the property in [rep:principalName] having value anonymous
>>>
>>> at 
>>> org.apache.jackrabbit.oak.spi.lifecycle.OakInitializer.initialize(OakInitializer.java:64)
>>> at org.apache.jackrabbit.oak.Oak.createContentRepository(Oak.java:551)
>>> at org.apache.jackrabbit.oak.jcr.Jcr.createRepository(Jcr.java:189)
>>> at 
>>> com.netenviron.content.manager.SessionManager.afterPropertiesSet(SessionManager.java:178)
>>>
>>>
>>> On 29 July 2014 17:34, Chetan Mehrotra <[email protected]> wrote:
>>>> With OAK-1997 the exception message should provide more details. Can
>>>> you try with latest from 1.x branch?
>>>> Chetan Mehrotra
>>>>
>>>>
>>>> On Tue, Jul 29, 2014 at 12:56 PM, Torgeir Veimo <[email protected]> 
>>>> wrote:
>>>>> Just starting up with a new repository now gives me an exception
>>>>> during repository configuration;
>>>>>
>>>>> java.lang.RuntimeException:
>>>>> org.apache.jackrabbit.oak.api.CommitFailedException:
>>>>> OakConstraint0030: Uniqueness constraint violated for key anonymous
>>>>>
>>>>> I initialize my repository using
>>>>>
>>>>> segmentStore = new FileStore(new File(oakRepositoryPath), 256);
>>>>> NodeStore nodeStore = new SegmentNodeStore(segmentStore);
>>>>>
>>>>> Oak oak = new Oak(nodeStore);
>>>>> Repository oakRepository = new Jcr(oak)
>>>>>   .with(new InitialContent())
>>>>>
>>>>>   .with(JcrConflictHandler.JCR_CONFLICT_HANDLER)
>>>>>   .with(new EditorHook(new VersionEditorProvider()))
>>>>>
>>>>>   .with(new SecurityProviderImpl())
>>>>>
>>>>>   .with(new ItemSaveValidatorProvider())
>>>>>   .with(new NameValidatorProvider())
>>>>>   .with(new NamespaceEditorProvider())
>>>>>   .with(new TypeEditorProvider())
>>>>>   .with(new ConflictValidatorProvider())
>>>>>   .with(new ReferenceEditorProvider())
>>>>>   .with(new ReferenceIndexProvider())
>>>>>
>>>>>   .with(new PropertyIndexEditorProvider())
>>>>>
>>>>>   .with(new PropertyIndexProvider())
>>>>>   .with(new OrderedPropertyIndexProvider())
>>>>>   .with(new NodeTypeIndexProvider())
>>>>>
>>>>>   .with(new OrderedPropertyIndexEditorProvider())
>>>>>
>>>>>   .createRepository();
>>>>>
>>>>>
>>>>> On 29 July 2014 16:50, Michael Dürig <[email protected]> wrote:
>>>>>>
>>>>>> Does this reproduce on a clean repo or only on the converted one? Do you
>>>>>> have a test case to reproduce this reliably?
>>>>>>
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>> On 29.7.14 7:32 , Torgeir Veimo wrote:
>>>>>>>
>>>>>>> Additional information, my dev repository is one converted from a
>>>>>>> jackrabbit repository. Can the warning be triggered not by the node
>>>>>>> that's being added, but by some nodes in the converted repository not
>>>>>>> being unique?
>>>>>>>
>>>>>>> On 29 July 2014 13:19, Torgeir Veimo <[email protected]> wrote:
>>>>>>>>
>>>>>>>> I am getting a lot of these,
>>>>>>>>
>>>>>>>> javax.jcr.nodetype.ConstraintViolationException: OakConstraint0030:
>>>>>>>> Uniqueness constraint violated for key
>>>>>>>> 42cd9011-84a8-485f-b723-435439ddcc71
>>>>>>>>
>>>>>>>> It seems to happen on session.save(), having just created a node of
>>>>>>>> type nt:unstructured, with a mixing node type which inherits
>>>>>>>> mix:referenceable.
>>>>>>>>
>>>>>>>> I can't seem to see any other pattern. Is there anything in particular
>>>>>>>> that could cause this, with code that worked ok with jackrabbit 2.8?
>>>>>>>>
>>>>>>>> This is with oak 1.0.3, but I've seen it on 1.0.1 and 1.0.2 as well.
>>>>>>>> --
>>>>>>>> -Tor
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -Tor
>>>
>>>
>>>
>>> --
>>> -Tor
>>
>>
>>
>> --
>> -Tor



-- 
-Tor

Reply via email to