You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/07/12 11:52:51 UTC
[jira] Created: (AMQ-2822) Stomp+nio transport fails sending byte
messages with NULL chars
Stomp+nio transport fails sending byte messages with NULL chars
---------------------------------------------------------------
Key: AMQ-2822
URL: https://issues.apache.org/activemq/browse/AMQ-2822
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.3.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.4.0
The problem is that routine for parsing commands doesn't take Content-length header into account, but only searches for the next NULL character.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2822) Stomp+nio transport fails sending byte
messages with NULL chars
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-2822.
--------------------------------
Resolution: Fixed
Fixed with svn revision 963282
> Stomp+nio transport fails sending byte messages with NULL chars
> ---------------------------------------------------------------
>
> Key: AMQ-2822
> URL: https://issues.apache.org/activemq/browse/AMQ-2822
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.0
>
>
> The problem is that routine for parsing commands doesn't take Content-length header into account, but only searches for the next NULL character.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.