Details
-
Bug
-
Resolution: Won't Do
-
Critical
-
None
-
5.4.3
-
None
-
None
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:
- magnolia
- holds default workspaces list
- points to mysql database named "author"
- uses local file system
- magnoliacluster-shared
- holds users, dam, dms, imaging and custom developed workspaces
- points to mysql database named "author"
- uses local file system
Public 1 has two sets of repositories:
- magnolia
- holds default workspaces list
- points to mysql database named "public"
- uses local file system
- magnoliacluster-shared
- holds users, dam, dms, imaging and custom developed workspaces
- points to mysql database named "author"
- NFS mount to authors file system
Public 2 has two sets of repositories:
- magnolia
- holds default workspaces list
- points to mysql database named "public"
- uses NFS mount to point to public 1 file system
- magnoliacluster-shared
- holds users, dam, dms, imaging and custom developed workspaces
- points to mysql database named "author"
- NFS mount to authors file system
Please also have a look at repositories.xml, to a get better picture
Checklists
Acceptance criteria