[
https://issues.apache.org/jira/browse/NIFI-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087053#comment-16087053
]
Koji Kawamura commented on NIFI-4169:
-------------------------------------
Hi [~ywik] again, for further detailed discussion, I wrote some code to
describe what might be implemented within PutWebSocket. I haven't even built it
so there's no guarantee if it works as expected, but essentially it will cover
what you need. Can you take a look and give me feedback?
https://github.com/ijokarumawak/nifi/commit/f5e50651a54be1b0403bf18ee60da139494de017
If you'd like to implement and contribute a PR, that's more than welcome! Let's
keep on discussion. Thanks!
> PutWebSocket processor with blank WebSocket session id attribute cannot
> transfer to failure queue
> -------------------------------------------------------------------------------------------------
>
> Key: NIFI-4169
> URL: https://issues.apache.org/jira/browse/NIFI-4169
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: Y Wikander
> Priority: Critical
> Labels: patch
> Attachments:
> 0001-websocket-when-sendMessage-fails-under-blank-session.patch
>
>
> If a PutWebSocket processor is setup with a blank WebSocket session id
> attribute (see NIFI-3318; Send message from PutWebSocket to all connected
> clients) and it is not connected to a websocket server it will log the
> failure and mark the flowfile with Success (rather than Failure) -- and the
> data is effectively lost.
> If there are multiple connected clients, and some succeed and others fail,
> routing Failure back into the PutWebSocket could result in duplicate data to
> some clients.
> Other NiFi processors seem to err on the side of "at least once".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
