[ https://issues.apache.org/jira/browse/PROTON-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459473#comment-17459473 ]
ASF subversion and git services commented on PROTON-2476: --------------------------------------------------------- Commit 89082f1eb4c1ca16407bc0a612b3b439868a2749 in qpid-proton's branch refs/heads/main from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=89082f1 ] PROTON-2476: Restore truncation behaviour for transfer frame traces The logging changes that came with PROTON-2448 had the side effect of no longer truncating the message payloads that came along with transfer frames. This meant that these trace lines could get extremely long if applications were sending long messages and could also take a very long time to allocate memory and format the string. > [proton-c] Trace level logging prints large transfer messages > ------------------------------------------------------------- > > Key: PROTON-2476 > URL: https://issues.apache.org/jira/browse/PROTON-2476 > Project: Qpid Proton > Issue Type: Test > Components: proton-c > Reporter: Ganesh Murthy > Priority: Major > > The transfer frames printed by proton trace level logging are very large. > This leads the Dispatch Travis CI to terminate the test run with the > following message > > {noformat} > The job exceeded the maximum log length, and has been terminated. {noformat} > [https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/551423517#L7947] > The large transfer frames can be seen here - > [https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/551423517#L7945] > > The transfer frames must be truncated. -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org