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
