Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/9302 list webmqtt connections prepr #1

Conversation

LoisSotoLopez
Copy link
Collaborator

No description provided.

@LoisSotoLopez LoisSotoLopez merged commit e8534ab into fix/9302-list-webmqtt-connections Mar 15, 2024
4 of 11 checks passed
@dentarg dentarg deleted the fix/9302-list-webmqtt-connections-prepr branch March 15, 2024 09:05
gomoripeti pushed a commit that referenced this pull request May 6, 2024
```
make -C deps/rabbit ct-amqp_system t=dotnet:fragmentation
```

fails in the new make CI with:
```
amqp_system_SUITE > dotnet > fragmentation
    #1. {error,{{badmatch,{error,134,
                                 "Unhandled exception. Amqp.AmqpException: Invalid frame size:527, maximum frame size:512.\n   at Amqp.Connection.ThrowIfClosed(String operation)\n   at Amqp.Connection.AddSession(Session session)\n   at Amqp.Session..ctor(Connection connection, Begin begin, OnBegin onBegin)\n   at Amqp.Session..ctor(Connection connection)\n   at Program.AmqpClient.connectWithOpen(String uri, Open opn) in /home/runner/work/rabbitmq-server/rabbitmq-server/deps/rabbit/test/amqp_system_SUITE_data/fsharp-tests/Program.fs:line 53\n   at Program.Test.fragmentation(String uri) in /home/runner/work/rabbitmq-server/rabbitmq-server/deps/rabbit/test/amqp_system_SUITE_data/fsharp-tests/Program.fs:line 284\n   at Program.main(String[] argv) in /home/runner/work/rabbitmq-server/rabbitmq-server/deps/rabbit/test/amqp_system_SUITE_data/fsharp-tests/Program.fs:line 533\n"}},
                [{amqp_system_SUITE,run_dotnet_test,2,
                                    [{file,"amqp_system_SUITE.erl"},
                                     {line,228}]},
                 {test_server,ts_tc,3,[{file,"test_server.erl"},{line,1793}]},
                 {test_server,run_test_case_eval1,6,
                              [{file,"test_server.erl"},{line,1302}]},
                 {test_server,run_test_case_eval,9,
                              [{file,"test_server.erl"},{line,1234}]}]}}
```

RabbitMQ includes its node name and cluster name in the open frame to
the client. Running this test locally shows an open frame size of 467
bytes.
The suspicion is that the node name and cluster name in CI is longer
causing the open frame from RabbitMQ to the client to exceed the frame size
of 512 bytes.
gomoripeti pushed a commit that referenced this pull request Oct 30, 2024
As described in rabbitmq#12413 (comment)
test case queue_topology flaked in CI with the following error:
```
rabbitmq_amqp_client > management_SUITE > cluster_size_3 > queue_topology
    #1. {error,{test_case_failed,{824,
                                  <<"rmq-ct-cluster_size_3-1-21000@localhost">>}}}
```

This flake could not be reproduced locally (neither with Mnesia nor with Khepri).
gomoripeti pushed a commit that referenced this pull request Nov 4, 2024
As described in rabbitmq#12413 (comment)
test case queue_topology flaked in CI with the following error:
```
rabbitmq_amqp_client > management_SUITE > cluster_size_3 > queue_topology
    #1. {error,{test_case_failed,{824,
                                  <<"rmq-ct-cluster_size_3-1-21000@localhost">>}}}
```

This flake could not be reproduced locally (neither with Mnesia nor with Khepri).
gomoripeti pushed a commit that referenced this pull request Nov 26, 2024
As described in rabbitmq#12413 (comment)
test case queue_topology flaked in CI with the following error:
```
rabbitmq_amqp_client > management_SUITE > cluster_size_3 > queue_topology
    #1. {error,{test_case_failed,{824,
                                  <<"rmq-ct-cluster_size_3-1-21000@localhost">>}}}
```

This flake could not be reproduced locally (neither with Mnesia nor with Khepri).

(cherry picked from commit 8c046c7)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant