Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7A3F3E0F3 for ; Mon, 28 Jan 2013 08:17:38 +0000 (UTC) Received: (qmail 63887 invoked by uid 500); 28 Jan 2013 08:17:38 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 63733 invoked by uid 500); 28 Jan 2013 08:17:37 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 63700 invoked by uid 99); 28 Jan 2013 08:17:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 08:17:36 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.ohr@gmail.com designates 209.85.128.51 as permitted sender) Received: from [209.85.128.51] (HELO mail-qe0-f51.google.com) (209.85.128.51) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 08:17:31 +0000 Received: by mail-qe0-f51.google.com with SMTP id 6so715882qea.24 for ; Mon, 28 Jan 2013 00:17:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=QH4bZyDfvP+RLv1GRPYvC8fySuNW1n7Jd9wsjgsMmzw=; b=YFy3Fq9zaem6pXYrId1gxDD5Ig4sPrnSlSToMZ89xVaww1p0dCKi6Uf8xUg6MWunZG PqcrsocFdn9mEjzJcVHTfUlge3BRANgG2dVzI93yiUC3vLbePWGtfDjriRPFlDjWpVN6 ndpoeq+0pinkAFpdGTVCdSupIc8V8QHYmHwYqydPEoSpmkQuqwzkhqU5Ewb34a8DiXtS Kf9wabc3nmkgyTg997aLCbFWcyU4BsunNuHgv3awRF0NmgiHWR+3FWA47n036w5UiafE C2x/YZouEx+IQQTQIS/VNmCYCMUkubTI+e01qjZu83j91mrqgeaN5RSZkxF1QQ0jdy3Y OsLA== MIME-Version: 1.0 X-Received: by 10.49.128.37 with SMTP id nl5mr17458621qeb.59.1359361030672; Mon, 28 Jan 2013 00:17:10 -0800 (PST) Received: by 10.49.27.234 with HTTP; Mon, 28 Jan 2013 00:17:10 -0800 (PST) In-Reply-To: <1359147089089-5726296.post@n5.nabble.com> References: <1359144448338-5726292.post@n5.nabble.com> <1359147089089-5726296.post@n5.nabble.com> Date: Mon, 28 Jan 2013 09:17:10 +0100 Message-ID: Subject: Re: HL7 Mina throwing org.apache.mina.filter.codec.ProtocolDecoderException: org.apache.mina.common.BufferDataException From: Christian Ohr To: users@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi Stan, try this ((I assume that hl7lp, hl7Port and minaLogger are properly set somewhere): from("mina:tcp://" + hl7Ip + ":" + hl7Port + "?sync=true&codec=#hl7codec&minaLogger=" + minaLogger) .... Registering the codec in Camel is not enough; you also need to add it as parameter to the endpoint URI. If you then still have problems, enable DEBUG logging for org.apache.camel.component.hl7. cheers Christian 2013/1/25 StanZ : > We're working in asynchronous mode where they send all of the messages and I > send the response back as each one is processed using ActveMQ for JMS > queuing. It worked fine in my own testing but is failing here. > > What I don't understand is the length of the message: 189616968 bytes > The hex for the message in the log is for one ADT message with only 6 > segments. It's pretty small so I'm not sure why or how the buffer length was > reached? > > If the sender sends async a continous stream with each message sparated by > the MLLP special characters, would the HL7MLLPCODEC cut off each one and > process separately? It may not be doing that. But then again the log HEX > only contains one HL7 message with starting and ending characters. > > > > -- > View this message in context: http://camel.465427.n5.nabble.com/HL7-Mina-throwing-org-apache-mina-filter-codec-ProtocolDecoderException-org-apache-mina-common-Buffen-tp5726292p5726296.html > Sent from the Camel - Users mailing list archive at Nabble.com.