[
https://issues.apache.org/jira/browse/DISPATCH-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated DISPATCH-1751:
-------------------------------------
Description:
On 32bit systems, an unexpected incoming-window value is set. This for example
causes system_tests_protocol_settings failures on 32bit systems, with test
expecting to see the incoming-window be 2147483647 but instead finding it much
less, e.g 131071.
This is due to the way the session capacity is configured, particularly on
32bit systems. See more details (output, code, etc) from prior discussions on
PROTON-2255 (raised when this was incorrectly thought to be a proton issue).
was:
On 32bit systems, an unexpected incoming-window value is set. This for example
causes system_tests_protocol_settings failures on 32bit systems:
{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 is due to the way the session capacity is configured, particularly on
32bit systems. See more details from prior discussion on PROTON-2255 when this
was incorrectly thought to be a proton issue.
> unexpected incoming-window in begin frame when running Dispatch on 32 bit
> system
> --------------------------------------------------------------------------------
>
> Key: DISPATCH-1751
> URL: https://issues.apache.org/jira/browse/DISPATCH-1751
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 1.13.0
> Reporter: Ganesh Murthy
> Priority: Major
>
> On 32bit systems, an unexpected incoming-window value is set. This for
> example causes system_tests_protocol_settings failures on 32bit systems, with
> test expecting to see the incoming-window be 2147483647 but instead finding
> it much less, e.g 131071.
> This is due to the way the session capacity is configured, particularly on
> 32bit systems. See more details (output, code, etc) from prior discussions on
> PROTON-2255 (raised when this was incorrectly thought to be a proton issue).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
