Re: DUCC 2.0.1 : JP Http Client Unable to Communicate with JD

Tue, 12 Jan 2016 02:28:59 -0800 

Adding to this, Jd is showing this log:

12 Jan 2016 15:25:52,028  INFO ActionGet - T[37] engage  seqNo=21 
remote=user.13895.34
[Fatal Error] :1:7109: 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>".
12 Jan 2016 15:25:52,071  WARN JD.log - J[N/A] T[36] 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:745)
Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 7109; 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.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)
        at 
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347)
        at 
com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:79)
        ... 26 more



On 01/12/2016 10:06 AM, reshu.agarwal wrote:


Hi,
I was getting this error after 17 out of 200 documents were processed. I am unable to find any reason for the same. Please see the error below:
INFO: Asynchronous Client Has Been Initialized. Serialization Strategy: [SerializationStrategy] Ready To Process. 
DuccAbstractProcessContainer.deploy() <<<<<<<< User Container deployed
.... Deployed Processing Container - Initialization Successful - Thread 32 
DuccAbstractProcessContainer.deploy() >>>>>>>>> Deploying User Container
....... UimaProcessContainer.doDeploy()
11 Jan 2016 17:18:36,969 INFO AgentSession - T[29] notifyAgentWithStatus ... Job Process State Changed - PID:24790. Process State: Initializing. JMX Url:N/A Dispatched State Update Event to Agent with IP:192.168.10.126 
DuccAbstractProcessContainer.deploy() <<<<<<<< User Container deployed
.... Deployed Processing Container - Initialization Successful - Thread 34 
DuccAbstractProcessContainer.deploy() >>>>>>>>> Deploying User Container
....... UimaProcessContainer.doDeploy()
DuccAbstractProcessContainer.deploy() <<<<<<<< User Container deployed
.... Deployed Processing Container - Initialization Successful - Thread 33 11 Jan 2016 17:18:38,277 INFO JobProcessComponent - T[33] setState Notifying Agent New State:Running 11 Jan 2016 17:18:38,279 INFO AgentSession - T[1] notifyAgentWithStatus ... Job Process State Changed - PID:24790. Process State: Running. JMX Url:service:jmx:rmi:///jndi/rmi://user:2106/jmxrmi Dispatched State Update Event to Agent with IP:192.168.10.126 11 Jan 2016 17:18:38,281 INFO AgentSession - T[33] notifyAgentWithStatus ... Job Process State Changed - PID:24790. Process State: Running. JMX Url:service:jmx:rmi:///jndi/rmi://user:2106/jmxrmi Dispatched State Update Event to Agent with IP:192.168.10.126 11 Jan 2016 17:18:38,281 INFO HttpWorkerThread - T[33] HttpWorkerThread.run() Begin Processing Work Items - Thread Id:33 11 Jan 2016 17:18:38,285 INFO HttpWorkerThread - T[34] HttpWorkerThread.run() Begin Processing Work Items - Thread Id:34 11 Jan 2016 17:18:38,285 INFO HttpWorkerThread - T[32] HttpWorkerThread.run() Begin Processing Work Items - Thread Id:32 11 Jan 2016 17:18:38,458 INFO HttpWorkerThread - T[34] run Thread:34 Recv'd WI:19 11 Jan 2016 17:18:38,468 INFO HttpWorkerThread - T[32] run Thread:32 Recv'd WI:18 11 Jan 2016 17:18:38,478 INFO HttpWorkerThread - T[33] run Thread:33 Recv'd WI:21 11 Jan 2016 17:18:38,515 ERROR DuccHttpClient - T[33] execute Unable to Communicate with JD - Error:HTTP/1.1 500 : 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>". 11 Jan 2016 17:18:38,515 ERROR DuccHttpClient - T[33] execute Content causing error:[B@3c0873f9 
Thread::33 ERRR::Content causing error:[B@3c0873f9
11 Jan 2016 17:18:38,516 ERROR DuccHttpClient - T[33] run
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 500 : 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.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
11 Jan 2016 17:18:38,535 ERROR DuccHttpClient - T[33] execute Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API 11 Jan 2016 17:18:38,535 ERROR DuccHttpClient - T[33] execute Content causing error:[B@12e81893 
Thread::33 ERRR::Content causing error:[B@12e81893
11 Jan 2016 17:18:38,535 ERROR DuccHttpClient - T[33] run
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API at org.apache.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
11 Jan 2016 17:18:38,535 ERROR HttpWorkerThread - T[33] run
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API at org.apache.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API at org.apache.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
11 Jan 2016 17:18:38,542 ERROR DuccHttpClient - T[33] execute Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API 11 Jan 2016 17:18:38,542 ERROR DuccHttpClient - T[33] execute Content causing error:[B@2d84416d 
Thread::33 ERRR::Content causing error:[B@2d84416d
11 Jan 2016 17:18:38,542 ERROR DuccHttpClient - T[33] run
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API at org.apache.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:168) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
11 Jan 2016 17:18:38,577 INFO HttpWorkerThread - T[33] run Thread:33 Recv'd WI:21 11 Jan 2016 17:18:38,592 ERROR DuccHttpClient - T[33] execute Unable to Communicate with JD - Error:HTTP/1.1 500 : 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>". 11 Jan 2016 17:18:38,592 ERROR DuccHttpClient - T[33] execute Content causing error:[B@6c798388 
Thread::33 ERRR::Content causing error:[B@6c798388
11 Jan 2016 17:18:38,592 ERROR DuccHttpClient - T[33] run
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 500 : 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.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
11 Jan 2016 17:18:38,599 ERROR DuccHttpClient - T[33] execute Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API 11 Jan 2016 17:18:38,600 ERROR DuccHttpClient - T[33] execute Content causing error:[B@7163eb69 
Thread::33 ERRR::Content causing error:[B@7163eb69
11 Jan 2016 17:18:38,600 ERROR DuccHttpClient - T[33] run
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API at org.apache.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
11 Jan 2016 17:18:38,600 ERROR HttpWorkerThread - T[33] run
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API at org.apache.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
java.lang.RuntimeException: JP Http Client Unable to Communicate with JD - Error:HTTP/1.1 501 Method n>POST is not defined in RFC 2068 and is not supported by the Servlet API at org.apache.uima.ducc.transport.configuration.jp.DuccHttpClient.execute(DuccHttpClient.java:226) at org.apache.uima.ducc.transport.configuration.jp.HttpWorkerThread.run(HttpWorkerThread.java:178) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.uima.ducc.transport.configuration.jp.UimaServiceThreadFactory$1.run(UimaServiceThreadFactory.java:85) 
    at java.lang.Thread.run(Thread.java:745)
Exiting Process Due to a Framework error
11 Jan 2016 17:18:38,601 ERROR HttpWorkerThread - T[33] run The Job Process Terminating Due To a Framework Error 

Thanks in advanvce.

Reshu.

Reply via email to