You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2012/10/29 15:16:13 UTC

[jira] [Resolved] (APLO-266) 1.2 with CRLF, sometimes gets: IOException: Unable to parse header line [\u0013]

     [ https://issues.apache.org/jira/browse/APLO-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-266.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5
         Assignee: Hiram Chirino

Thanks for the test cases.  I've now applied a fix and it's being deployed in the following CI build:
https://builds.apache.org/job/ActiveMQ-Apollo-Deploy/311/console

I think the CRLF inconsistency should also be resolved now.  Apollo should always delivery messages with just NL headers now.
                
> 1.2 with CRLF, sometimes gets: IOException: Unable to parse header line [\u0013]
> --------------------------------------------------------------------------------
>
>                 Key: APLO-266
>                 URL: https://issues.apache.org/jira/browse/APLO-266
>             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
>            Assignee: Hiram Chirino
>             Fix For: 1.5
>
>         Attachments: letest2.rb, letest3.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  | java.io.IOException: Unable to parse header line [\u0013] | org.apache.activemq.apollo.broker.Broker | 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: http://www.atlassian.com/software/jira