[ 
https://issues.apache.org/jira/browse/UIMA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103234#comment-15103234
 ] 

Lou DeGenaro commented on UIMA-4757:
------------------------------------

08 Jan 2016 16:58:10,607  INFO ActionGet - T[27] engage  seqNo=114 
remote=host.domain.31589.52
[Fatal Error] :1:4113: The element type 
"org.apache.uima.ducc.container.net.impl.MetaCasTransaction" must be terminated 
by the matching end-tag 
"</org.apache.uima.ducc.container.net.impl.MetaCasTransaction>".
08 Jan 2016 16:58:10,673  WARN JD.log - J[N/A] T[34] engage /jdApp
com.thoughtworks.xstream.io.StreamException:  : The element type 
"org.apache.uima.ducc.container.net.impl.MetaCasTransaction" must be terminated 
by the matching end-tag 
"</org.apache.uima.ducc.container.net.impl.MetaCasTransaction>".
        at 
com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:86)
        at 
com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:66)
        at com.thoughtworks.xstream.XStream.fromXML(XStream.java:853)
        at com.thoughtworks.xstream.XStream.fromXML(XStream.java:845)
        at 
org.apache.uima.ducc.common.utils.XStreamUtils.unmarshall(XStreamUtils.java:35)
        at 
org.apache.uima.ducc.transport.configuration.jd.JobDriverConfiguration$JDServlet.doPost(JobDriverConfiguration.java:240)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:538)
        at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:478)
        at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
        at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:937)
        at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
        at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
        at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:871)
        at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
        at org.eclipse.jetty.server.Server.handle(Server.java:346)
        at 
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:589)
        at 
org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1065)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:823)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:220)
        at 
org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411)
        at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:535)
        at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
        at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
        at java.lang.Thread.run(Thread.java:780)
Caused by: org.xml.sax.SAXParseException: The element type 
"org.apache.uima.ducc.container.net.impl.MetaCasTransaction" must be terminated 
by the matching end-tag 
"</org.apache.uima.ducc.container.net.impl.MetaCasTransaction>".
        at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at 
com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:79)
        ... 26 more



> DUCC Job Driver (JD) swallows serialization errors?
> ---------------------------------------------------
>
>                 Key: UIMA-4757
>                 URL: https://issues.apache.org/jira/browse/UIMA-4757
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.1.0-Ducc
>
>
> Then it is possible that the XMI serializer threw an exception which was 
> caught and ignored by the JD. Instead the JD should not send out the CAS, but 
> simply convert this exception into a WI error and attach the error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to