<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: In Apache  NIFI requests are queued and showing socket timeout exception ,not getting processed in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378753#M243659</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/107711"&gt;@Rohit1997jio&lt;/a&gt;&amp;nbsp; If your endpoint test works with Postman, and your invokeHttp is setup similary, the above error suggest the nifi node cannot connect to the endpoint.&amp;nbsp; You would need to ensure you have network connectivity from nifi host to endpoint.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Nov 2023 15:36:37 GMT</pubDate>
    <dc:creator>steven-matison</dc:creator>
    <dc:date>2023-11-08T15:36:37Z</dc:date>
    <item>
      <title>In Apache  NIFI requests are queued and showing socket timeout exception ,not getting processed</title>
      <link>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378743#M243652</link>
      <description>&lt;P&gt;1000 requests are queued in NIFI , invoke HTTP processor is showing socket timeout exception , i have added a self loop in invoke http processor so that it keep on retrying . These requests are stuck permanently.&lt;/P&gt;&lt;P&gt;My issue is endpoint which invoke http processor is trying to invoke is up and running .&amp;nbsp; i checked from postman i am able to get success response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2023-11-08 12:17:34,783 ERROR [Timer-Driven Process Thread-138] o.a.nifi.processors.standard.InvokeHTTP InvokeHTTP[id=b48ff3b8-befb-32c2-b670-83445e1873f2] Routing to Failure due to exception: java.net.SocketTimeoutException: connect timed out: java.net.SocketTimeoutException: connect timed out&lt;BR /&gt;java.net.SocketTimeoutException: connect timed out&lt;BR /&gt;at java.net.PlainSocketImpl.socketConnect(Native Method)&lt;BR /&gt;at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:476)&lt;BR /&gt;at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:218)&lt;BR /&gt;at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:200)&lt;BR /&gt;at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:394)&lt;BR /&gt;at java.net.Socket.connect(Socket.java:606)&lt;BR /&gt;at okhttp3.internal.platform.Platform.connectSocket(Platform.java:124)&lt;BR /&gt;at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:223)&lt;BR /&gt;at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:149)&lt;BR /&gt;at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:195)&lt;BR /&gt;at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:121)&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 09:37:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378743#M243652</guid>
      <dc:creator>Rohit1997jio</dc:creator>
      <dc:date>2023-11-08T09:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: In Apache  NIFI requests are queued and showing socket timeout exception ,not getting processed</title>
      <link>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378753#M243659</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/107711"&gt;@Rohit1997jio&lt;/a&gt;&amp;nbsp; If your endpoint test works with Postman, and your invokeHttp is setup similary, the above error suggest the nifi node cannot connect to the endpoint.&amp;nbsp; You would need to ensure you have network connectivity from nifi host to endpoint.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 15:36:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378753#M243659</guid>
      <dc:creator>steven-matison</dc:creator>
      <dc:date>2023-11-08T15:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: In Apache  NIFI requests are queued and showing socket timeout exception ,not getting processed</title>
      <link>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378768#M243664</link>
      <description>&lt;P&gt;i created a new flow with same end points , some requests are getting successful , but still few requests are still getting stuck in invoke http processor giving socket timeout exception&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 17:29:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378768#M243664</guid>
      <dc:creator>Rohit1997jio</dc:creator>
      <dc:date>2023-11-08T17:29:00Z</dc:date>
    </item>
    <item>
      <title>Re: In Apache  NIFI requests are queued and showing socket timeout exception ,not getting processed</title>
      <link>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378952#M243733</link>
      <description>&lt;P&gt;Sometimes I need to increase the timeouts in the processor configurations.&amp;nbsp; &amp;nbsp; You may also need to reduce the execution time for the processor incase the endpoint cannot handle too many requests at once.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 15:03:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/378952#M243733</guid>
      <dc:creator>steven-matison</dc:creator>
      <dc:date>2023-11-13T15:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: In Apache  NIFI requests are queued and showing socket timeout exception ,not getting processed</title>
      <link>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/390503#M247276</link>
      <description>&lt;P&gt;Did you find any solution about this issue ? I have exactly the same problem.&lt;/P&gt;&lt;P&gt;An invoke HTTP get a time out on the flow file. A retry is implemented and the flow file get stucked with a timeout each time.&lt;/P&gt;&lt;P&gt;Works fine with same configuration to call API with postman and a curl from server nifi node.&lt;/P&gt;&lt;P&gt;The only way is to restart the invoke http processor and after few hours and some flow files a new occurence appears.&lt;/P&gt;&lt;P&gt;Error :&lt;/P&gt;&lt;P&gt;2024-07-17 14:55:06,783 ERROR [Timer-Driven Process Thread-17] o.a.nifi.processors.standard.InvokeHTTP InvokeHTTP[id=ba9d2024-8df1-323d-b0ba-54402272b188] Routing to Failure due to exception: java.net.SocketTimeoutException: timeout: java.net.SocketTimeoutException: timeout&lt;BR /&gt;java.net.SocketTimeoutException: timeout&lt;BR /&gt;at okhttp3.internal.http2.Http2Stream$StreamTimeout.newTimeoutException(Http2Stream.java:593)&lt;BR /&gt;at okhttp3.internal.http2.Http2Stream$StreamTimeout.exitAndThrowIfTimedOut(Http2Stream.java:601)&lt;BR /&gt;at okhttp3.internal.http2.Http2Stream$FramingSink.emitFrame(Http2Stream.java:510)&lt;BR /&gt;at okhttp3.internal.http2.Http2Stream$FramingSink.close(Http2Stream.java:538)&lt;BR /&gt;at okio.RealBufferedSink.close(RealBufferedSink.java:236)&lt;BR /&gt;at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:63)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)&lt;BR /&gt;at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)&lt;BR /&gt;at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)&lt;BR /&gt;at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)&lt;BR /&gt;at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)&lt;BR /&gt;at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)&lt;BR /&gt;at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)&lt;BR /&gt;at okhttp3.RealCall.execute(RealCall.java:69)&lt;BR /&gt;at org.apache.nifi.processors.standard.InvokeHTTP.onTrigger(InvokeHTTP.java:850)&lt;BR /&gt;at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)&lt;BR /&gt;at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1174)&lt;BR /&gt;at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:213)&lt;BR /&gt;at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)&lt;BR /&gt;at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)&lt;BR /&gt;at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)&lt;BR /&gt;at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)&lt;BR /&gt;at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)&lt;BR /&gt;at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)&lt;BR /&gt;at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)&lt;BR /&gt;at java.base/java.lang.Thread.run(Thread.java:834)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2024 14:22:53 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/In-Apache-NIFI-requests-are-queued-and-showing-socket/m-p/390503#M247276</guid>
      <dc:creator>dupuy_gregory</dc:creator>
      <dc:date>2024-07-17T14:22:53Z</dc:date>
    </item>
  </channel>
</rss>

