[ https://issues.apache.org/jira/browse/PROTON-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173961#comment-17173961 ]
Robbie Gemmell commented on PROTON-2255: ---------------------------------------- I'd agree it's much less consequential now we know what/why it happens. The issue before was we didn't know, and it could have had much more serious implications depending on what was occurring. It's also not a proton bug either way it seems, which again we didn't know before looking. Still points to odd behaviour from Dispatch (actually explicitly enabling a non-effective level of session flow control when thinking/indicating it's basically disabled). > [proton-c] unexpected incoming-window in begin frame when running Dispatch > test in 32 bit system > ------------------------------------------------------------------------------------------------ > > Key: PROTON-2255 > URL: https://issues.apache.org/jira/browse/PROTON-2255 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c > Affects Versions: proton-c-0.31.0 > Reporter: Ganesh Murthy > Priority: Major > > system_tests_protocol_settings fails in Dispatch with the following error > > {noformat} > ====================================================================== > FAIL: test_connector_default > (system_tests_protocol_settings.ConnectorSettingsDefaultTest) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File > "/home/jenkins/workspace/rh-qpid-dispatch-dist-el6-32-master/build/BUILD/qpid-dispatch-1.13.0/tests/system_tests_protocol_settings.py", > line 343, in test_connector_default > self.assertTrue(" incoming-window=2147483647," in begin_lines[0]) > AssertionError: False is not True > ====================================================================== > FAIL: test_max_frame_max_session_zero > (system_tests_protocol_settings.MaxFrameMaxSessionFramesZeroTest) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File > "/home/jenkins/workspace/rh-qpid-dispatch-dist-el6-32-master/build/BUILD/qpid-dispatch-1.13.0/tests/system_tests_protocol_settings.py", > line 287, in test_max_frame_max_session_zero > self.assertTrue(" incoming-window=2147483647," in begin_lines[0]) > AssertionError: False is not True > ====================================================================== > FAIL: test_max_session_frames_default > (system_tests_protocol_settings.MaxSessionFramesDefaultTest) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File > "/home/jenkins/workspace/rh-qpid-dispatch-dist-el6-32-master/build/BUILD/qpid-dispatch-1.13.0/tests/system_tests_protocol_settings.py", > line 249, in test_max_session_frames_default > self.assertTrue(" incoming-window=2147483647," in begin_lines[0]) > AssertionError: False is not True {noformat} > > The actual line in the log is > {noformat} > 2020-07-30 12:47:53.727396 -0400 PROTOCOL (trace) [3]:FRAME: 0 <- > @begin(17) [next-outgoing-id=0, incoming-window=131071, > outgoing-window=2147483647] > (/root/project/build/BUILD/qpid-dispatch-1.13.0/src/server.c:112) {noformat} > > The test is expecting to see the incoming-window to be 2147483647 but instead > gets 131071. > This could be a possible issue with the way the incoming-window is logged but > really not sure. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org