activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] [Commented] (APLO-266) 1.2 with CRLF, sometimes gets: IOException: Unable to parse header line [\u0013]
Date Fri, 26 Oct 2012 19:21:13 GMT


Hiram Chirino commented on APLO-266:

Yeah the 'mix mode' is allowed in 1.2.  Specifically what's causing the mixed mode is that
message headers that were originally sent /w  CRLF, preserve the CRLF, but new headers which
the broker adds to the message only have LF.  Technically that is allowed by the 1.2 spec.
 But I do think it would nicer the broker make them more consistent.
> 1.2 with CRLF, sometimes gets: IOException: Unable to parse header line [\u0013]
> --------------------------------------------------------------------------------
>                 Key: APLO-266
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-stomp
>         Environment: Ubuntu 11.10
> Ruby (various versions)
> AMD Phenom(tm) II X6 1055T Processor
> 16GB RAM
> apache-apollo-99-trunk-20120929.031419-121-unix-distro.tar.gz
>            Reporter: Guy Allard
>         Attachments: letest2.rb
> I am testing Stomp 1.2 functionality that uses CRLF line ends.
> Under some conditions, sending a frame with \r\n line ends results in, e.g.:
> 2012-10-26 12:25:07,258 | WARN  | Unable to parse header line [\u0013]
| | hawtdispatch-DEFAULT-1
> This does not happen all the time.
> I do have a somewhat lengthy (but straightforward) program that recreates this.  I will
attach it shortly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message