Closed loicmathieu closed 3 years ago
Hey @loicmathieu
This package is simply a wrapper over rhea providing promise versions of the APIs exposed in rhea.
Can you share more on what this ORIGINAL_ENCODING
is? I don't see any such AMQP property being set in either this package or rhea.
Also, from what you have explained above, the issue seems to be around encoding which is done in rhea. I would recommend moving this issue to https://github.com/amqp/rhea
@ramya-rao-a I no longuer use this package as I move to a different projet. I agree the issue is on rhea side. As I no longuer need this, I'll close the issue.
Describe the bug I have a component based on
rhea-promise
that sends AMQP messages. I want those messages to be received by a Java component.Here is how I send a message with
rhea-promise
.I can successfully receive the same message in my Java component if send from a Java component.
I check the messages using JMSToolbox and the message contents are the same, the AMQP headers are the same except
ORIGINAL_ENCODING
that has the value 2 when the message is sent from my Java component and 5 when send fromrhea-promise
.So, I suspect the cause of the issue is that my Java component and rhea-promise didn't handle the same way the
ORIGINAL_ENCODING
AMQP property.Is there a way to fix this value to 5 ?
I also try to directly send my user object but then the
ORIGINAL_ENCODING
property has the value 7 and it didn't work either.Package-version: node.js version: v10.19.0 OS name and version: Linux 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux