[
https://issues.apache.org/jira/browse/NIFI-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-2259:
--------------------------------
Summary: HTTP Site-to-Site doesn't handle TRANSACTION_FINISHED
_BUT_DESTINATION_FULL as expected (was: HTTP Site-to-Site doesn't handle
TRANSACTION_FINISHED _BUT_DESTINATION_FULL)
> HTTP Site-to-Site doesn't handle TRANSACTION_FINISHED _BUT_DESTINATION_FULL
> as expected
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-2259
> URL: https://issues.apache.org/jira/browse/NIFI-2259
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Fix For: 1.0.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> If a remote NiFi instance input-port's destination becomes full, It's
> expected that remote NiFi instance returns
> TRANSACTION_FINISHED_BUT_DESTINATION_FULL response.
> However, an IOException occurred due to DESTINATION_FULL handshake error when
> org.apache.nifi.remote.Transaction.complete() is called.
> The cause of this issue is SiteToSiteResource.commitInputPortTransaction()
> checks if all of input-port's destination is full. Which shouldn't be
> executed at complete(). The transaction is already committed on source NiFi.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
