[MGNLPER-112] Periscope prevents deploying Public webapp as ROOT along with Author in the same Tomcat Created: 05/Jun/19  Updated: 23/Jun/20  Resolved: 23/Jun/20

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: 1.0, 1.1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Not an issue Votes: 2
Labels: maintenance, nd4j
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2020-04-07-08-53-44-999.png     Text File log-two-authors.txt     Text File mgnl-error-log.txt    
Issue Links:
Problem/Incident
causality
caused by MGNLPER-73 magnolia.bootstrap.authorInstance pro... Closed
dependency
depends upon MGNLPER-73 magnolia.bootstrap.authorInstance pro... Closed
is depended upon by MGNLPER-120 DOC: A howto for mgnlper-112 - perisc... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Periscope improvements

 Description   

Steps to reproduce:

  1. Download Enterprise Pro MTE demo Tomcat bundle 6.0
  2. Finish the installation of the author first, then continue to the public
  3. Make sure that both of them are up and running. Then stop your Tomcat
  4. Rename magnoliaPublic folder to ROOT, start it again
  5. If I logged in to author first, then when I login to public (ROOT), the issue happen. Reverse the sequence when I logged in to public (ROOT) first, then when I login to author, the issue happen for the author side. I have already tried with different browsers logins.


 Comments   
Comment by Ilgun Ilgun [ 05/Jun/19 ]

This is in fact introduced by MGNLPER-73, In the startup of MGNL we simply rely on observedComponent 'ServerConfiguration' which is populated by JCR configuration. That in fact means we have no configuration when we install MGNL for the first time hence we don't have the notion of author or public before we install. Ideal solution should include double check one for configuration file and other one for ServerConfiguration.

Comment by Viet Nguyen [ 06/Jun/19 ]

This is not an issue anymore as its related issue has been fixed and would be released in our up-coming 6.1 per ilgun comment below.

Comment by Viet Nguyen [ 06/Jun/19 ]

Thanks ilgun for checking and confirming the issue.

Comment by Jonathan Ayala [ 26/Jul/19 ]

Seems that the error also appears in 6.1 when deploying two author instances in same tomcat, it still happens although none of them are ROOT. However, if they are public and author, it doesn't happen.

Steps to reproduce with  Enterprise Pro MTE demo Tomcat bundle 6.1

  1. Change public instance to author through configuration
  2. Restart tomcat
  3. Login in the admin central in one of the authors: Everything OK
  4. Login in the admin central in the other author: Error appears in log java.lang.NoClassDefFoundError: Could not initialize class org.nd4j.linalg.factory.Nd4j log-two-authors.txt and search doesn't work
Comment by Mariusz Chruscielewski [ 05/Sep/19 ]

I'm also experiencing that problem @Viet

. I get NoClassDefFound error's and search doesn't work in author

Comment by Viet Nguyen [ 06/Sep/19 ]

Hello mchruscielewski,

The issue has not been fixed but it was closed somehow, anyway first of all please split your 2 instances into 2 separated Tomcat as a work around solution. We - Magnolia Supporters - already informed our development team to schedule a fix. Thank you for using and reporting issue with us.

Cheers,
Viet

Comment by Marvin Kerkhoff [ 18/Oct/19 ]

Hi We also facing this issue. In our installation we have 2 seperated Tomcats. It's still there. Same Stacktraces.

Comment by Jonathan Ayala [ 18/Oct/19 ]

According to SUPPORT-10494 it's been reproduced in separated tomcats as well, located in same virtual machine (probably same JDK).

Comment by Mariusz Chruscielewski [ 08/Nov/19 ]

I confirm, it happens on 2 tomcat instances, running on same virtual machine and same JDK

Comment by Mariusz Chruscielewski [ 12/Nov/19 ]

Any news on this issue? It prevents us from deploying to production for one of customers. Do you have any plans and date where this can be fixed?

Comment by Marvin Kerkhoff [ 12/Nov/19 ]

Hi @Mariusz: you can remove magnolia-periscope-result-ranker-1.1.jar from your WAR Package. Then the Search is shown but it's not ranked. This should only be a temporary solutions until Magnolia is fixing the issue. For me it was working. Please let me know how the search performs on your environment. For me it was not that fast as i expected. But i am realy not sure if it's the environment in generell or has something to do with removing the JAR.

Comment by Simon Lutz [ 14/Nov/19 ]

Hi mchruscielewski, marvink2,

we have changed this issue from a bug a to an improvement. The ndj4 library can only be initiated once, thus result ranking on public instances is disabled too. We will clarify and properly document the current limitations. I will comment here again once done.

For now, marvink2's suggestion is the way to go.

Simon

Comment by Marvin Kerkhoff [ 14/Nov/19 ]

Hi @Simon,

i am ok with it. Please provide some documentation about how to disable it on public instances.

Thanks
Marvin

Comment by Marvin Kerkhoff [ 07/Apr/20 ]

Hi Magnolians,

with the new Version 6.1.5 i am able to fix the issues i had with the ranking. I deactivated the ranking module. But i still see a memory decrease. It has probably something to do with this:

I am currently not able to update to 6.2. Do you have a workaround for this?

Thanks

Marvin

Comment by Simon Lutz [ 07/Apr/20 ]

Hi marvink2,

could you please create a new SUPPORT-ticket summarizing your issues? We do not fully understand how it related to updating to 6.2. Our support-team will help you further.

Thank you,
Simon

Comment by Simon Lutz [ 23/Jun/20 ]

Documented as known issue: https://documentation.magnolia-cms.com/display/DOCS/Known+issues#Knownissues-PeriscopepreventsdeployingthepublicwebappasROOTalongwiththeauthorinstance

Closing this ticket therefore.

Generated at Mon Feb 12 10:28:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.