You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Firenz (Jira)" <ji...@apache.org> on 2019/09/20 18:34:00 UTC
[jira] [Updated] (NIFI-6697) HandleHttpRequest - 500, stopping does
not works
[ https://issues.apache.org/jira/browse/NIFI-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Firenz updated NIFI-6697:
-------------------------
Description:
My HandleHTTPRequest does not accept anymore POST messages, after some time, returning 500 (port 10010).
There is lot of file availaible on the machine (ulimit etc).
Settings :
* 1 thread
* timerdriver
* 200ms
* 50 containerqueue (i'm pretty sure i never fill it due to low volumes of calls).
"Stop Processor" does not work : it starts the stop thread, never ending.
"Terminate Thread" seems to work (the #2 on the processor disappears), but a thread dump shows that *not* :
{code:java}
/"qtp920046370-777080-acceptor-0@367cdcb6-ServerConnector@6962170f{HTTP/1.1,[http/1.1]}{0.0.0.0:10010}" Id=777080 RUNNABLE
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
waiting on java.lang.Object@3b97aac8 at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
waiting on java.lang.Object@3b97aac8 at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:369) at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:639) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680) at java.lang.Thread.run(Unknown Source)
{code}
The listener is still there :
{code:java}
netstat -an | grep 10010
tcp 0 0 0.0.0.0:10010 0.0.0.0:* LISTEN {code}
Restarting the processor (after the "terminate thread") does not work since the port is already listening.
Current workaround : stop/start nifi.
was:
My HandleHTTPRequest does not accept anymore POST messages, after some time, returning 500.
Settings : 1thread, timerdriver, 200ms, 50 containerqueue.
Stop does not work. Terminate thread seems to work, but a thread dump show that not :
"qtp920046370-777080-acceptor-0@367cdcb6-ServerConnector@6962170f\{HTTP/1.1,[http/1.1]}{0.0.0.0:10010}" Id=777080 RUNNABLE
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
- waiting on java.lang.Object@3b97aac8
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
- waiting on java.lang.Object@3b97aac8
at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:369)
at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:639)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)
at java.lang.Thread.run(Unknown Source)
The listener is still there :
netstat -an | grep 10010
tcp 0 0 0.0.0.0:10010 0.0.0.0:* LISTEN
Restart the processor (after a terminatethread) does not work since the port is already listening.
Current workaround : stop/start
> HandleHttpRequest - 500, stopping does not works
> ------------------------------------------------
>
> Key: NIFI-6697
> URL: https://issues.apache.org/jira/browse/NIFI-6697
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.8.0
> Environment: CentOS Linux release 7.5.1804 (Core)
> Oracle jre1.8.0_181-amd64
> Reporter: Firenz
> Priority: Critical
>
> My HandleHTTPRequest does not accept anymore POST messages, after some time, returning 500 (port 10010).
> There is lot of file availaible on the machine (ulimit etc).
> Settings :
> * 1 thread
> * timerdriver
> * 200ms
> * 50 containerqueue (i'm pretty sure i never fill it due to low volumes of calls).
> "Stop Processor" does not work : it starts the stop thread, never ending.
> "Terminate Thread" seems to work (the #2 on the processor disappears), but a thread dump shows that *not* :
> {code:java}
> /"qtp920046370-777080-acceptor-0@367cdcb6-ServerConnector@6962170f{HTTP/1.1,[http/1.1]}{0.0.0.0:10010}" Id=777080 RUNNABLE
> at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
> at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
> waiting on java.lang.Object@3b97aac8 at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
> waiting on java.lang.Object@3b97aac8 at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:369) at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:639) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680) at java.lang.Thread.run(Unknown Source)
> {code}
>
> The listener is still there :
>
> {code:java}
> netstat -an | grep 10010
> tcp 0 0 0.0.0.0:10010 0.0.0.0:* LISTEN {code}
>
> Restarting the processor (after the "terminate thread") does not work since the port is already listening.
>
> Current workaround : stop/start nifi.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)