Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Sat, 27 Oct 2012 16:49:12 +0000 (UTC)
From: "Guy Allard (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: <852842668.35366.1351356552705.JavaMail.jiratomcat@arcas>
In-Reply-To: <1927294962.32536.1351269913077.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (APLO-266) 1.2 with CRLF, sometimes gets:
 IOException: Unable to parse header line [\u0013]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Guy Allard updated APLO-266:
----------------------------

    Attachment: letest3.rb

This is a significantly shorter example that triggers the described behavior.

                
> 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
>         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