Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2084

List message is received as List in List using qpid-cpp client

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • Jboss A-MQ 7.0.0
    • JBoss A-MQ 6.2.1
    • None
    • Hide

      1. send a list message with qpid-cpp client to A-MQ6 broker (ie,: ['String'])
      2. receive the list message
      3. the content is received as List with one element that contains the List message sent (ie.: [['String']])

      Show
      1. send a list message with qpid-cpp client to A-MQ6 broker (ie,: ['String'] ) 2. receive the list message 3. the content is received as List with one element that contains the List message sent (ie.: [ ['String'] ])

      When a list message is sent to and received from the A-MQ6.2.1 broker, the received message contains List with one element that is the originally sent List (i.e:: if I send ['String'] in the message content the received massage has [['String']] in its content). Content_type used is 'amqp/list'.

      This is some kind of regression as A-MQ6.3.0 and Qpidd brokers do not suffer from that.

      There is a Formatter class that do the output for the QE clients and the List object is obtained by msg.getContentObject().asList() API call. If this call is done on message in the sender code, the list is retrieved as expected ['String'], but when the call is done in receiver code it outputs [['String']].

      I'm not completely sure where the issues lies. When testing with A-MQ6.3.0 and Qpidd brokers the List content is received as expected, that implies it shall be A-MQ6.2.1 broker issue. On the other hand when the message (sent by qpid-cpp client to A-MQ6.2.1) is received with other client (qpid-jms, python-proton) the message is received as expected, that point to client issue. If it's a client library issue please feel free to change component accordingly.

              Unassigned Unassigned
              tkratky_jira Tomas Kratky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: