Open wshager opened 8 years ago
not sure about your idea if Xerces. But... that is /exist/apps/benjamins/new/journal_issues/content/customers/mailinglist/catalog/sl.26.1
? A collection? a binary resource?
@dizzzz that's a path from the controller, but it doesn't resolve anything (as it's incorrect).
but who does set this path? what is is the issue? what means "quits" ? How does the code looks like? I just don't understand your ticket.... There is soo little info.
@dizzzz exist exits and restarts itself, we're having trouble tracking down the reason, but I did want to mention it. Investigations continue.
really restarts? ouch!
are you running existdb with the service wrapper? is so, please check the wrapper.log too ;
please state version: 2.x ? 3.x ?
@dizzzz hmm this is the log from that day, but the timestamp is slightly off.
INFO | jvm 1 | 2016/04/14 10:16:24 | [Fatal Error] :1:1: Content is not allowed in prolog. STATUS | wrapper | 2016/04/14 16:33:29 | TERM trapped. Shutting down. ERROR | wrapper | 2016/04/14 16:34:28 | Shutdown failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2016/04/14 16:34:28 | JVM did not exit on request, termination requested. STATUS | wrapper | 2016/04/14 16:34:28 | JVM received a signal SIGKILL (9). STATUS | wrapper | 2016/04/14 16:34:28 | JVM process is gone. STATUS | wrapper | 2016/04/14 16:34:28 | JVM exited after being requested to terminate. STATUS | wrapper | 2016/04/14 16:34:29 | <-- Wrapper Stopped STATUS | wrapper | 2016/04/14 16:37:14 | --> Wrapper Started as Daemon STATUS | wrapper | 2016/04/14 16:37:14 | Java Service Wrapper Community Edition 64-bit 3.5.26 STATUS | wrapper | 2016/04/14 16:37:14 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2016/04/14 16:37:14 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2016/04/14 16:37:14 | STATUS | wrapper | 2016/04/14 16:37:15 | Launching a JVM...
@dizzzz after the log entry I posted there's some "journal scanning" and another reboot that I probably did manually.
@dizzzz sorry, this doesn't help. I can't seem to find the log back...
@dizzzz unfortunately I deleted the exist.log of april 16, which was the correct date. The wrapper.log says exactly what I have pasted (SIGKILL 9), only from 2016/04/16 13:54:45. I think I messed up the log posting due to stress...
@dizzzz below is the correct log posting I sent to @wolfgangmm. It's roughly the same error, and there's also quite a difference in the timestamp. I wonder why?
2016-04-16 13:17:03,749 [eXistThread-263648] WARN (ServletHandler.java [doHandle]:563) - /exist/apps/benjamins/catalog/books/content/catalog/pumrl javax.servlet.ServletException: Error while serializing xml: javax.xml.transform.TransformerException: org.eclipse.jetty.io.EofException
@dizzzz in both cases the path to the controller is messed up, so there may be a pattern here. Possibly there's a configuration error in my app, but I'd never be able to reproduce this path. The "content" path never follows the "catalog" path: both may only appear after "benjamins". The repeating "catalog" is a bad sign.
Another finding: when I access the above paths directly, there's no error in the logs.
is anybody still seeing shutdowns related to EoF and xml.transform. If not I propose to close.
Just for bookkeeping, because I haven't a clue... Exist spontaneously quits when it encounters a org.eclipse.jetty.io.EofException after a javax.xml.transform.TransformerException after a javax.servlet.ServletException: Error while serializing xml.
Curious thing is that this seems to me a Xerces related error (unless I'm utterly mistaken) while I run Saxon...