on 06-05-2019 9:45 AM
Since updating to 6.4.0.22 we are experiencing an issue within our hybris cluster. After certain time (mostly about 3-4 workdays) random nodes show a 500 server error after login to backoffice.
In the log of the node I can find the following Error:
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | SCHWERWIEGEND: Servlet.service() for servlet [zkLoader] in context with path [/backoffice] threw exception [Servlet execution threw an exception] with root cause
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | java.lang.StackOverflowError
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at java.util.WeakHashMap.getTable(WeakHashMap.java:350)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at java.util.WeakHashMap.get(WeakHashMap.java:397)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.ClassFactory.create0(ClassFactory.java:88)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.createInstance(ClassBeanInfoImpl.java:282)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.createInstance(UnmarshallingContext.java:623)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.runtime.unmarshaller.StructureLoader.startElement(StructureLoader.java:185)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:501)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:480)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(InterningXmlVisitor.java:75)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:150)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:244)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:250)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:250)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:250)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:250)
INFO | jvm 1 | main | 2019/06/05 07:12:27.105 | at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281)
I can "fix" this by logging in to another node and resetting the config from there.
What I checked so far: The media file (mount) is still accessible by the node affected by the 500 server error (Media with code cockpitng*) The server did not show any strange behavior before the 500 server error occurred
Is this a known bug and does anyone else also experience this?
Unfortunately we never found a solution and are therefore monitoring removing from balancing and restarting the app-server automatically
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi johannes_neubauer , monatguvenir . Did you find the solution for that issue? Also have the similar error
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi johannes_neubauer,
Did you find solution for this? We have this error on our application.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.