You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Marcel Patzlaff (JIRA)" <ji...@apache.org> on 2007/10/02 18:20:22 UTC
[jira] Reopened: (AMQ-670) STOMP not setting content-length on byte
messages.
[ https://issues.apache.org/activemq/browse/AMQ-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Patzlaff reopened AMQ-670:
---------------------------------
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.
> STOMP not setting content-length on byte messages.
> --------------------------------------------------
>
> Key: AMQ-670
> URL: https://issues.apache.org/activemq/browse/AMQ-670
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 4.0 RC2
>
>
> It was also setting the content-length as a propertly on the JMS message when receiving a binary message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.