AEM Author not starting | Community
Skip to main content
Level 2
January 30, 2017
Solved

AEM Author not starting

  • January 30, 2017
  • 5 replies
  • 2608 views

Hi All,

I am facing slowness in the local AEM authoring instance(1 hour to load author instance) and getting the below message in

error.log file
---------------
31.01.2017 00:03:49.461 *WARN* [FelixStartLevel] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=SELECT * FROM [nt:base] WHERE [jcr:uuid] = $id /* oak-internal */, path=*, property=[jcr:uuid=[9400a0e8-5d7e-36ad-bb8a-2ce8783a9281]]); consider creating an index or changing the query
31.01.2017 00:03:49.541 *WARN* [FelixStartLevel] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 2000 nodes with filter Filter(query=SELECT * FROM [nt:base] WHERE [jcr:uuid] = $id /* oak-internal */, path=*, property=[jcr:uuid=[9400a0e8-5d7e-36ad-bb8a-2ce8783a9281]]); consider creating an index or changing the query
31.01.2017 00:03:49.624 *WARN* [FelixStartLevel] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 3000 nodes with filter Filter(query=SELECT * FROM [nt:base] WHERE [jcr:uuid] = $id /* oak-internal */, path=*, property=[jcr:uuid=[9400a0e8-5d7e-36ad-bb8a-2ce8783a9281]]); consider creating an index or changing the query
.
.
.

31.01.2017 00:11:31.982 *WARN* [FelixStartLevel] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 517000 nodes with filter Filter(query=SELECT * FROM [nt:base] WHERE [jcr:uuid] = $id /* oak-internal */, path=*, property=[jcr:uuid=[e2484592-c2a2-3917-9040-a5432d4c9d2c]]); consider creating an index or changing the query

stderr.log
----------
Low-memory action set to fork
Using 32bit VM settings, min.heap=768MB, min permgen=192MB, default fork arguments=[-Xmx768m, -XX:MaxPermSize=192m]
**** WARNING: insufficent heap memory ******************************************
The JVM reports 742 MB but we recommend at least 768 MB +/- 20
Use your JVM's heap size option (like -Xmx768M) to set that size.

ENV: AEM 6.1

Please suggest me if any configuration change require to improve the performance.

Thanks in Advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by kautuk_sahni

Hi 

Please have a look at this forum thread:

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.1.html/forum__ywgo-hi_our_aem_61i.html

Here member faced similar issue.

~kautuk

5 replies

smacdonald2008
Level 10
January 30, 2017

It would appear you have an indexing issue. THis log message points that out: 

org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 517000 nodes

Watch this session on Indexing: 

https://docs.adobe.com/ddc/en/gems/oak-lucene-indexes.html

joerghoh
Adobe Employee
Adobe Employee
January 30, 2017

HI,

please check if you have an index covering the jcr:uuid properties (should be /oak:index/uuid).

Jörg

Level 2
January 31, 2017

Thanks macdonald and Jorg for response.

Now I am not able to access CRXDE/any other URL and getting 403 forbidden error on server startup and below in error.log

error.log
31.01.2017 22:35:37.572 *ERROR* [pool-7-thread-3] org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job execution of org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@1493607 : null
java.lang.IllegalStateException: null
 
Is there any other way to check this issue?

kautuk_sahni
Community Manager
kautuk_sahniCommunity ManagerAccepted solution
Community Manager
February 1, 2017
Kautuk Sahni