ActiveMQ
  1. ActiveMQ
  2. AMQ-670

STOMP not setting content-length on byte messages.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0
    • Component/s: Transport
    • Labels:
      None

      Description

      It was also setting the content-length as a propertly on the JMS message when receiving a binary message.

      1. send.rb
        0.4 kB
        Hiram Chirino
      2. recv.rb
        0.4 kB
        Hiram Chirino

        Activity

        Hide
        Hiram Chirino added a comment -

        fixed.

        Show
        Hiram Chirino added a comment - fixed.
        Hide
        Marcel Patzlaff added a comment -

        When I send a STOMP (binary) message with a specified "content-length" header to the broker and try to receive it with another STOMP-Client then the second one does not receive this "content-length" header. I do not know where it gets lost but especially for binary messages this header is essential.

        Show
        Marcel Patzlaff added a comment - When I send a STOMP (binary) message with a specified "content-length" header to the broker and try to receive it with another STOMP-Client then the second one does not receive this "content-length" header. I do not know where it gets lost but especially for binary messages this header is essential.
        Hide
        Hiram Chirino added a comment -

        script used to test reported error

        Show
        Hiram Chirino added a comment - script used to test reported error
        Hide
        Hiram Chirino added a comment -

        script used to test reported error

        Show
        Hiram Chirino added a comment - script used to test reported error
        Hide
        Hiram Chirino added a comment -

        I used the attached send.rb and recv.rb script to test sending a receiving a message with the content-length header set and it seem to work fine against the activemq trunk.

        Closing issue out again as fixed on 5.0

        Show
        Hiram Chirino added a comment - I used the attached send.rb and recv.rb script to test sending a receiving a message with the content-length header set and it seem to work fine against the activemq trunk. Closing issue out again as fixed on 5.0

          People

          • Assignee:
            Hiram Chirino
            Reporter:
            Hiram Chirino
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development