You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Tjad Clark (JIRA)" <ji...@apache.org> on 2013/05/26 15:35:23 UTC
[jira] [Comment Edited] (QPID-4835) JMS client is unable to read
the application headers of messages sent by the ruby clients
[ https://issues.apache.org/jira/browse/QPID-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667321#comment-13667321 ]
Tjad Clark edited comment on QPID-4835 at 5/26/13 1:33 PM:
-----------------------------------------------------------
I can confirm this issue.
I think the issue is that the client - perhaps because of the wrapper-, is sending the type as VBIN instead of a plain String. And the headers on the JMS side that are seen to be headers are only the basic types, String, Boolean and Int/Long .. I have debugged sending Strings as the properties of the message, the key comes out fine, however the value of the header comes as a byte[] .. because it is a VBIN (0x90).
I have played around with the wrapper, trying all sorts of different ways to send a std::string, it keeps being sent across as a VBIN.. I am not sure why.. I haven't tried with the python client or the plain C++ client.. so it really confuses me, that those headers are fine.. I thought it would be a wrapper issue according to the above description.. But my findings say otherwise..
Could someone test ?
was (Author: coral):
I can confirm this issue.
I think the issue is that the client - perhaps because of the wrapper-, is sending the type as VBIN instead of a plain String. And the headers on the JMS side that are seen to be headers are only the basic types, String, Boolean and Int/Long .. I have debugged sending Strings as the properties of the message, the key comes out fine, however the value of the header comes as a byte[] .. because it is a VBIN (0x90).
I have played around with the wrapper, trying all sorts of different ways to send a std::string, it keeps being sent across as a VBIN.. I am not sure why.. I haven't tried with the python client or the plain C++ client.. so it really confuses me, that those headers are fine.. I thought it would be a wrapper issue, but the above description says otherwise.. Could someone test ?
> JMS client is unable to read the application headers of messages sent by the ruby clients
> -----------------------------------------------------------------------------------------
>
> Key: QPID-4835
> URL: https://issues.apache.org/jira/browse/QPID-4835
> Project: Qpid
> Issue Type: Bug
> Components: Ruby Client
> Affects Versions: 0.20
> Reporter: Petr Matousek
> Assignee: Darryl L. Pierce
>
> I was unable to read the application headers of messages sent by the ruby example client (spout) using the JMS example client.
> ie.
> # cd /usr/lib/ruby/gems/1.8/gems/qpid_messaging-0.20.2/examples
> # ruby spout.rb -P foo=bar q
> # cd /usr/share/doc/qpid-java-0.22/examples
> # ./run_example.sh org.apache.qpid.example.Drain q | grep Properties
> Properties:<NONE>
> Properties of the received message shall list 'foo = bar'.
> note: JMS client can read application headers of messages sent by c++/python.
> packages used:
> ruby gem: qpid_messaging-0.20.2
> java Drain example from qpid-0.22
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org