Versions Compared

Old Version 26

changes.mady.by.user Ashraf Khamis

Saved on

compared with

New Version 27

changes.mady.by.user Martin Drápela

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: + MGNLPER-120

...

Until the JCR bug is fixed, do not use searchfn. To get the correct order, execute JCR XPath queries directly.

DL4J issues

There are limitations related to the deep learning and search features of the Find bar, which are provided by the Periscope and Periscope Result Ranker modules.

Off-heap memory starvation

You should configure DL4J memory limits to avoid off-heap memory starvation. This is particularly the case with the -Dorg.bytedeco.javacpp.maxbytes JVM argument. For more details, see MGNLPER-121.

Periscope prevents deploying the public webapp as ROOT along with the author instance

When experiencing this issue, the following message can be found in the logs: java.lang.NoClassDefFoundError: Could not initialize class org.nd4j.linalg.factory. The issue may appear even on more than just one Tomcat instance, running on the same VM and the same JDK.

The ndj4 library can only be initiated once. Therefore, result ranking on public instances should be disabled, which you can do either by changing the configuration of the Periscope Result Ranker module, or rather by completely removing the magnolia-periscope-result-ranker module from your WAR package. After this modification, the search function will be available but search results will not be ranked. For more details see MGNLPER-112.