[MAGNOLIA-6695] Instances gradually die when in multi-clustered environment Created: 14/Jun/16  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.3
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Gediminas Zalys Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File error.log     XML File repositories.xml    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Instance dies after intermittent amount of time, from 20minutes to 6hours, but never lasts for more than a day.

No strange logs before death, nonetheless see logs snippet below for preview, full trace attached:

Jun 14, 2016 2:53:21 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance.
Jun 14, 2016 2:53:21 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Jun 14, 2016 2:53:22 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
Jun 14, 2016 2:53:22 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Jun 14, 2016 2:53:22 PM org.apache.catalina.core.ApplicationContext log
INFO: Destroying Spring FrameworkServlet 'rest'
Jun 14, 2016 2:53:22 PM com.vaadin.event.ListenerMethod writeObject
WARNING: Error in serialization of the application: Class info.magnolia.ui.admincentral.AdmincentralVaadinServlet$1$1 must implement serialization.
Jun 14, 2016 2:53:22 PM org.apache.catalina.session.StandardSession writeObject
WARNING: Cannot serialize session attribute com.vaadin.server.VaadinSession.AdminCentral for session 1AC4EB995557B3DA7D0A57C0045369B0
java.io.NotSerializableException: org.apache.catalina.loader.WebappClassLoader
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)

If clustering is removed all instances (Author and public 1) is stable for days .... If multiple publics are added instance, server life time becomes very short.

Setup is as follow:

Author has two sets of repositories:

  1. magnolia
    1. holds default workspaces list
    2. points to mysql database named "author"
    3. uses local file system
  2. magnoliacluster-shared
    1. holds users, dam, dms, imaging and custom developed workspaces
    2. points to mysql database named "author"
    3. uses local file system

Public 1 has two sets of repositories:

  1. magnolia
    1. holds default workspaces list
    2. points to mysql database named "public"
    3. uses local file system
  2. magnoliacluster-shared
    1. holds users, dam, dms, imaging and custom developed workspaces
    2. points to mysql database named "author"
    3. NFS mount to authors file system

Public 2 has two sets of repositories:

  1. magnolia
    1. holds default workspaces list
    2. points to mysql database named "public"
    3. uses NFS mount to point to public 1 file system
  2. magnoliacluster-shared
    1. holds users, dam, dms, imaging and custom developed workspaces
    2. points to mysql database named "author"
    3. NFS mount to authors file system

Please also have a look at repositories.xml, to a get better picture



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:16:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.