[jira] [Commented] (NIFI-9478) Improve Netty exception logging

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460315#comment-17460315 ] 

ASF subversion and git services commented on NIFI-9478:
-------------------------------------------------------

Commit 5e9c86885ce4557f41a955adcaa3a6e70df3f501 in nifi's branch refs/heads/main from Nathan Gough
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5e9c868 ]

NIFI-9478 Moved Netty Log Exception Handler to end of pipeline

- Changed display name of Max Number of TCP Connections to Max Number of Worker Threads for ListenTCP
- Set Netty Socket Receive Buffer using Max Socket Buffer Size in ListenTCP

This closes #5599

Signed-off-by: David Handermann <ex...@apache.org>


> Improve Netty exception logging
> -------------------------------
>
>                 Key: NIFI-9478
>                 URL: https://issues.apache.org/jira/browse/NIFI-9478
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.16.0
>            Reporter: Nathan Gough
>            Assignee: Nathan Gough
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> ListenTCP does not show a WARN message when a frame is dropped due its size being larger than 'Receive Buffer Size', which appears to be a result of the exception log handling in netty. This may affect other processors now using netty. The exception log handler should be at the end of the netty handler pipeline.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)