Hello Robert et all,

Thank you for your reply.  I have not been able to pair down to a sample project that isolates this issue. I'm currently deploying my application over and over until I hit the failure mode. I haven't identified the code that would have created the missing primary types.  I could use some ideas on where to look next, even if it is just a best guess.

In the failed state I can see that the component org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager is active according the Felix Webconsole. But there is no corresponding service of the type org.apache.sling.jcr.api.SlingRepository.   This may another version of the information the logs are telling me. But it is something I noticed trying to compare working and not working instances.

Any ideas would be helpful at this point. I was kind of hoping that the log messages might trigger an "oh yeah, I've seen this before in X" kind of moment, since I currently have no purchase on the problem.

Thank you,

Marc



14.02.2019 12:28:29.190 *WARN*[CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.jackrabbit.oak.segment.SegmentNodeStoreService)] org.apache.sling.commons.scheduler.impl.QuartzScheduler Scheduler job requested thread pool with name oak but this thread pool is not in the list of allowed pools. 14.02.2019 12:28:29.453 *WARN*[Apache Sling Repository Startup Thread] org.apache.jackrabbit.oak.plugins.name.NameValidator Invalid namespace prefix([, sv, nt, xml, jcr, oak, rep, mix]): slingevent 14.02.2019 12:28:29.454 *WARN*[Apache Sling Repository Startup Thread] org.apache.jackrabbit.oak.plugins.name.NameValidator Invalid namespace prefix([, sv, nt, xml, jcr, oak, rep, mix]): sling 14.02.2019 12:28:29.455 *WARN*[Apache Sling Repository Startup Thread] org.apache.jackrabbit.oak.plugins.name.NameValidator Invalid namespace prefix([, sv, nt, xml, jcr, oak, rep, mix]): sling 14.02.2019 12:28:29.455 *WARN*[Apache Sling Repository Startup Thread] org.apache.jackrabbit.oak.plugins.name.NameValidator Invalid namespace prefix([, sv, nt, xml, jcr, oak, rep, mix]): sling 14.02.2019 12:28:29.456 *WARN*[Apache Sling Repository Startup Thread] org.apache.jackrabbit.oak.plugins.name.NameValidator Invalid namespace prefix([, sv, nt, xml, jcr, oak, rep, mix]): sling 14.02.2019 12:28:29.904 *ERROR*[Apache Sling Repository Startup Thread] org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager start: Uncaught Throwable trying to access Repository, calling stopRepository() java.lang.RuntimeException: org.apache.jackrabbit.oak.api.CommitFailedException: OakConstraint0001: /oak:index/jcrLanguage/:index[[]]: The primary type null does not exist         at org.apache.jackrabbit.oak.OakInitializer.initialize(OakInitializer.java:50)
        at org.apache.jackrabbit.oak.Oak.initialContent(Oak.java:682)
        at org.apache.jackrabbit.oak.Oak.createNewContentRepository(Oak.java:725)         at org.apache.jackrabbit.oak.Oak.createContentRepository(Oak.java:670)         at org.apache.jackrabbit.oak.jcr.Jcr.createContentRepository(Jcr.java:376)         at org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager.acquireRepository(OakSlingRepositoryManager.java:152)         at org.apache.sling.jcr.base.AbstractSlingRepositoryManager.initializeAndRegisterRepositoryService(AbstractSlingRepositoryManager.java:471)         at org.apache.sling.jcr.base.AbstractSlingRepositoryManager.access$300(AbstractSlingRepositoryManager.java:85)         at org.apache.sling.jcr.base.AbstractSlingRepositoryManager$4.run(AbstractSlingRepositoryManager.java:455) Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakConstraint0001: /oak:index/jcrLanguage/:index[[]]: The primary type null does not exist

On 2/15/19 10:51 AM, Robert Munteanu wrote:
Hi Marc,

On Thu, 2019-02-14 at 16:02 -0500, [email protected] wrote:
I've been moderately successful. However, about
1/2 the time, our application will fail to deploy. I can not parse
if
this is a Oak failure or a sling10 failure, or a configuration
between
the two issue. I'm looking for any insight as to what this might be.
A sample project reproducing the issue would be very helpful.

Thanks,

Robert

Reply via email to