ActiveMQ
  1. ActiveMQ
  2. AMQ-739

STOMP transport handles JMS type improperly

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 4.0, 4.0.1
    • Fix Version/s: None
    • Component/s: Transport
    • Labels:
      None
    • Environment:

      sending from STOMP to JMS

      Description

      Sending a text message from a stomp client with a content-length results in a bytes message on JMS. Suggest doing the following ...

      1) The stomp transport should always add the content-length header to out-going messages, regardless of content-type or whether or not a content-length was provided on the incoming message.
      2) The stomp transport should handle in-coming messages with a content-type header, and should pass that through.
      3) If a message comes in without a content-length or a content-type, it should just be assumed a TextMessage. This way we can use the terminating null character as the delimiter.

        Activity

          People

          • Assignee:
            Nathan Mittler
            Reporter:
            Nathan Mittler
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 168h
              168h
              Remaining:
              Remaining Estimate - 168h
              168h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development