Jahia JCR indexing slowing down with JBoss

Solution Verified - Updated -

Environment

JBoss Enterprise Application Platform 4.3.0.GA_CP08 + customisations.

Issue

We’re trying to install the Jahia CMS on our JBoss platform configured with a JCR connected to an Oracle database as backend.

When starting for the first time, Jahia tries to initialize JCR indexes by using the Apache JackRabbit content repository and an Apache Lucene database frameworks. We noticed that this process is extremely slow with this configuration. We tried different configurations to find out what is causing this slowing down, and we suspect that something has changed in our version of JBoss EAP.

JBoss EAP vanilla version + Oracle database : 12 minutes
JBoss EAP our customized version + Oracle database : more than 2 hours

When our platform was set up 2 years ago, we know that several modifications have been done to the configuration and to the directory structure, but we can’t figure out what could cause this behaviour.

Resolution

Move the jdbc driver (ojdbc6.jar) from lib ext directory.

Root Cause

The slowing was caused by having the jdbc driver (ojdbc6.jar) in lib ext directory.

Diagnostic Steps

Analyse logs and generate and analyse thread dumps to see if there is anything obviously wrong.
Analyse jvm start up options used.
Compared customised version with the vanilla version.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.