-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Fix amqp091->amqp10 shovel with complex headers #13798
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
Conversation
application properties. Before this change, trying to shovel dead-lettered messages from an AMQP 0.9.1 source to AMQP 1.0 destination would fail with: ``` reason: {badarg, [{unicode,characters_to_binary, [[{table, [{<<"count">>,long,1}, {<<"reason">>,longstr,<<"maxlen">>}, {<<"queue">>,longstr,<<"tmp">>}, {<<"time">>,timestamp,1745575728}, {<<"exchange">>,longstr,<<>>}, {<<"routing-keys">>,array, [{longstr,<<"tmp">>}]}]}]], [{file,"unicode.erl"}, {line,1219}, {error_info,#{module => erl_stdlib_errors}}]}, {amqp10_client_types,utf8,1, [{file,"amqp10_client_types.erl"},{line,99}]}, {amqp10_msg,'-set_application_properties/2-fun-0-',3, [{file,"amqp10_msg.erl"},{line,385}]}, {maps,fold_1,4,[{file,"maps.erl"},{line,860}]}, {amqp10_msg,set_application_properties,2, [{file,"amqp10_msg.erl"},{line,384}]}, {maps,fold_1,4,[{file,"maps.erl"},{line,860}]}, {rabbit_amqp10_shovel,forward,4, [{file,"rabbit_amqp10_shovel.erl"},{line,337}]}, {rabbit_shovel_worker,handle_info,2, [{file,"rabbit_shovel_worker.erl"},{line,104}]}]} ```
c4bf535
to
c5271ea
Compare
@mkuratczyk @ansd should we backport this to patch releases? It seems to be a safe change and a genuine bug fix to me. |
I think it is fine to backport this yes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is fine for now until we can make use of the proper conversions in mc
Fix amqp091->amqp10 shovel with complex headers (backport #13798)
Some AMQP 0.9.1 headers, in particular x-death headers, cannot be set as application properties. Before this change, trying to shovel dead-lettered messages from an AMQP 0.9.1 source to AMQP 1.0 destination would fail with:
Fixes #13797