将 StreamMessage 从 CMS 发送到 JMS
我正在尝试将 ActiveMQ StreamMessage 从 C++ (CMS) 客户端发送到 Java (JMS) 客户端。但是，Java 客户端无法正确读取传入消息中的值 - 大多数字段都被提取为 null，并且确实具有与其关联的值的字段似乎包含垃圾。
我可以很好地从 C++ 客户端向 Java 客户端发送 BytesMessages 和 TextMessages，因此 BytesMessage 现在是我们的后备。
然而，行为不当的 StreamMessage 让我们怀疑两个客户端之间存在问题/不兼容。
我们在 Java 端使用 ActiveMQ 5.4.2，在 C++ 端使用 activemq-cpp 3.0.1。
JMS 和 CMS 实现之间是否存在任何已知的不兼容性，或者是否有任何其他我应该寻找的明显陷阱？
I am trying to send an ActiveMQ StreamMessage from a C++ (CMS) client to a Java (JMS) client. However, the Java client is unable to correctly read the values from the incoming message - most fields are extracted as null, and the fields that do have values associated with them just seem to contain garbage.
I can send BytesMessages and TextMessages from our C++ client to our Java client just fine, so the BytesMessage is our fallback for now.
However, the misbehaving StreamMessage is making us suspect something is wrong/incompatible between our two clients.
We are using ActiveMQ 5.4.2 on the Java side, and activemq-cpp 3.0.1 on the C++ side.
Are there any known incompatibilities between the JMS and CMS implementations, or are there any other obvious pitfalls I should look for?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为我在 3.0.1 和最新的 3.2.4 之间修复了一些问题，修复了流消息的一些问题。我强烈建议您更新到 CMS v3.2.4，因为修复了大量错误，并提供了一些很棒的新功能。
如果您想查看自您使用的版本以来已修复的问题，CMS 问题跟踪器位于此处使用：
编辑：找到修复它的问题，位于此处。
-蒂姆
www.fusesource.com
I think there were some issues that I fixed somewhere between 3.0.1 and the latest 3.2.4 that fixed some issues with stream message. I'd really recommend that you update to v3.2.4 of CMS as there's been a large number of bugs fixed, along with some great new features.
The CMS issue tracker is here if you want to review to issues fixed since the version you are using:
Edit: Found the issue that fixed it, its here.
-Tim
www.fusesource.com