Troubleshooting Community troubleshooting
This section contains common concerns and known issues when troubleshooting Community.
Known Issues known-issues
Dispatcher Refetch Fails dispatcher-refetch-fails
When using Dispatcher 4.1.5 with a newer version of Jetty, a refetch may result in ‘Unable to receive response from remote server’ after waiting for the request to time out.
Using Dispatcher 4.1.6 or later resolves this issue.
Cannot Access Forum Post After Upgrading from CQ 5.4 cannot-access-forum-post-after-upgrading-from-cq
If a forum was created on CQ 5.4 and topics posted, and then the site was upgraded to AEM 5.6.1 or later, attempting to view the existing posts may result in an error on the page:
Illegal pattern character ‘a’
Cannot serve request to /content/demoforums/forum-test.html on this server and the logs contain the following:
20.03.2014 22:49:35.805 ERROR [10.177.45.32 [1395380975744] GET /content/demoforums/forum-test.html HTTP/1.1] com.day.cq.wcm.tags.IncludeTag Error while executing script content.jsp
org.apache.sling.api.scripting.ScriptEvaluationException:
at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388)
at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:171)
The issue is that the format string for com.day.cq.commons.date.RelativeTimeFormat was changed between 5.4 and 5.5 such that the “a” for “ago” is no longer accepted.
Thus, any code using RelativeTimeFormat() API must change:
- From:
final RelativeTimeFormat fmt = new RelativeTimeFormat("r a", resourceBundle); - To:
final RelativeTimeFormat fmt = new RelativeTimeFormat("r", resourceBundle);
The failure is different on Author and Publish. On Author, it fails silently and simply does not display the forum topics. On Publish, it throws up the error on the page.
See the com.day.cq.commons.date.RelativeTimeFormat API for more information.
Common Concerns common-concerns
Warning in Logs: Handlebars Deprecated warning-in-logs-handlebars-deprecated
During startup (not the first - but every one after that) the following warning may be seen in the logs:
11.04.2014 08:38:07.223 WARN [FelixStartLevel]com.github.jknack.handlebars.Handlebars Helper 'i18n'has been replaced bycom.adobe.cq.social.handlebars.I18nHelper@15bac645
This warning can be safely ignored as jknack.handlebars.Handlebars, used by SCF, comes with its own i18n helper utility. On startup, it is replaced with an AEM-specific i18n helper. This warning is generated by the third-party library to confirm the override of an existing helper.
Warning in Logs: OakResourceListener processOsgiEventQueue warning-in-logs-oakresourcelistener-processosgieventqueue
Posting several Social Communities forum topics may result in huge quantities of warning and info logs from OakResourceListener processOsgiEventQueue.
These warnings can be safely ignored.
23.04.2014 14:21:18.900 *WARN* [pool-5-thread-3] org.apache.sling.jcr.resource.internal.OakResourceListener processOsgiEventQueue: Resource at /var/search-collections/ugc-sc/_m.frq/jcr:content not found, which is not expected for an added or modified node
23.04.2014 14:21:18.908 *WARN* [pool-5-thread-3] org.apache.sling.jcr.resource.internal.OakResourceListener processOsgiEventQueue: Resource at /var/search-collections/ugc-sc/_m.prx/jcr:content not found, which is not expected for an added or modified node
23.04.2014 14:21:18.909 *WARN* [pool-5-thread-3] org.apache.sling.jcr.resource.internal.OakResourceListener processOsgiEventQueue: Resource at /var/replication/data/1f799fb4-0aeb-4660-aadb-705657f16048/67/67699ab5-9d57-4c79-a755-2727ba9e6452/jcr:content not found, which is not expected for an added or modified node
23.04.2014 14:21:18.909 *WARN* [pool-5-thread-3] org.apache.sling.jcr.resource.internal.OakResourceListener processOsgiEventQueue: Resource at /var/replication/data/1f799fb4-0aeb-4660-aadb-705657f16048/67/67699ab5-9d57-4c79-a755-2727ba9e6452/jcr:content not found, which is not expected for an added or modified node
23.04.2014 14:21:18.990 *WARN* [pool-5-thread-3] org.apache.sling.jcr.resource.internal.OakResourceListener processOsgiEventQueue: Resource at /var/replication/data/1f799fb4-0aeb-4660-aadb-705657f16048/b9/b91f1690-87e8-41d8-a78e-cd2259f837c8/jcr:content not found, which is not expected for an added or modified node
23.04.2014 14:21:18.990 *WARN* [pool-5-thread-3] org.apache.sling.jcr.resource.internal.OakResourceListener processOsgiEventQueue: Resource at /var/replication/data/1f799fb4-0aeb-4660-aadb-705657f16048/b9/b91f1690-87e8-41d8-a78e-cd2259f837c8/jcr:content not found, which is not expected for an added or modified node
Error in Logs: NoClassDefFoundError for IndexElementFactory error-in-logs-noclassdeffounderror-for-indexelementfactory
Upgrading AEM 5.6.1 to the latest cq-socialcommunities-pkg-1.4.x, or to AEM 6.0 results in errors in the log file. This occurs during startup for a condition which resolves itself as evidenced by the error not being seen on restart.
14.11.2013 20:52:39.453 ERROR [Apache Sling JCR Resource Event Queue Processor for path '/'] com.adobe.cq.social.storage.index.impl.IndexService Error occurred while processing event java.util.ConcurrentModificationException
14.11.2013 20:52:40.716 ERROR [OsgiInstallerImpl] com.adobe.cq.social.cq-social-commons [CommentListProvider] Error during instantiation of the implementation object (java.lang.NoClassDefFoundError: com/adobe/cq/social/storage/index/IndexElementFactory) java.lang.NoClassDefFoundError: com/adobe/cq/social/storage/index/IndexElementFactory
14.11.2013 20:52:40.717 ERROR [OsgiInstallerImpl] com.adobe.cq.social.cq-social-commons [CommentListProvider] Failed creating the component instance; see log for reason