[
https://issues.apache.org/jira/browse/NIFI-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318786#comment-15318786
]
ASF GitHub Bot commented on NIFI-1857:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/497
@ijokarumawak I can't seem to get this to work properly. I configured nifi
to allow http site-to-site only, not secure. I then connected a
GenerateFlowFile processor to a Remote Process Group that points back to
http://localhost:8080/nifi with the only port that I have. I ensured that the
port was running and transferring data to an UpdateAttribute processor that
ends the flow. When I start sending data to the RPG, though, no data is sent,
and the logs show the following every 60 seconds:
```
2016-06-07 12:14:44,902 WARN [I/O dispatcher 89]
o.a.n.r.util.SiteToSiteRestApiClient Didn't received additional packet to send,
nor confirm transaction call for 30001 millis which exceeds idle connection
expiration millis(30000). This transaction will timeout.
2016-06-07 12:14:44,902 ERROR [I/O dispatcher 89]
o.a.n.r.util.SiteToSiteRestApiClient Sending data to
http://127.0.0.1:8080/nifi-api/site-to-site/input-ports/84cd8e54-68ba-41ff-a1a3-ffc445836a8f/transactions/dddd06ca-3912-4a8f-9e81-fff68d8c0e96/flow-files
has failed
java.io.IOException: Didn't received additional packet to send, nor confirm
transaction call for 30001 millis
at
org.apache.nifi.remote.util.SiteToSiteRestApiClient$3.produceContent(SiteToSiteRestApiClient.java:504)
~[nifi-site-to-site-client-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.http.impl.nio.client.MainClientExec.produceContent(MainClientExec.java:262)
~[httpasyncclient-4.1.1.jar:4.1.1]
at
org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.produceContent(DefaultClientExchangeHandlerImpl.java:136)
~[httpasyncclient-4.1.1.jar:4.1.1]
at
org.apache.http.nio.protocol.HttpAsyncRequestExecutor.outputReady(HttpAsyncRequestExecutor.java:240)
~[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.DefaultNHttpClientConnection.produceOutput(DefaultNHttpClientConnection.java:292)
~[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.client.InternalIODispatch.onOutputReady(InternalIODispatch.java:86)
[httpasyncclient-4.1.1.jar:4.1.1]
at
org.apache.http.impl.nio.client.InternalIODispatch.onOutputReady(InternalIODispatch.java:39)
[httpasyncclient-4.1.1.jar:4.1.1]
at
org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:147)
[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:190)
[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:343)
[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:317)
[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:278)
[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
[httpcore-nio-4.4.4.jar:4.4.4]
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:590)
[httpcore-nio-4.4.4.jar:4.4.4]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
```
> Support HTTP(S) as a transport mechanism for Site-to-Site
> ---------------------------------------------------------
>
> Key: NIFI-1857
> URL: https://issues.apache.org/jira/browse/NIFI-1857
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> We should add support for using HTTP(S) for site-to-site to be an alternative
> to the current socket based approach.
> This would support the same push based or pull based approach site-to-site
> offers now but it would use HTTP(S) for all interactions to include learning
> about ports, learning about NCM topology, and actually exchanging data. This
> mechanism should also support interaction via an HTTP proxy.
> This would also require some UI work to allow the user to specify which
> protocol for site-to-site to use such as 'raw' vs 'http'. We also need to
> document any limitations with regard to SSL support for this mode and we'd
> need to provide 'how-to' when using proxies like http_proxy or something else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
