Return-Path: X-Original-To: apmail-activemq-commits-archive@www.apache.org Delivered-To: apmail-activemq-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D370DD3B5 for ; Fri, 26 Oct 2012 19:21:15 +0000 (UTC) Received: (qmail 44419 invoked by uid 500); 26 Oct 2012 19:21:13 -0000 Delivered-To: apmail-activemq-commits-archive@activemq.apache.org Received: (qmail 44386 invoked by uid 500); 26 Oct 2012 19:21:13 -0000 Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list commits@activemq.apache.org Received: (qmail 44330 invoked by uid 99); 26 Oct 2012 19:21:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct 2012 19:21:13 +0000 Date: Fri, 26 Oct 2012 19:21:13 +0000 (UTC) From: "Hiram Chirino (JIRA)" To: commits@activemq.apache.org Message-ID: <712418039.33124.1351279273203.JavaMail.jiratomcat@arcas> In-Reply-To: <1927294962.32536.1351269913077.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/APLO-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485131#comment-13485131 ] 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: 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 > > > 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