Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 52794 invoked from network); 22 May 2008 14:27:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 May 2008 14:27:28 -0000 Received: (qmail 35681 invoked by uid 500); 22 May 2008 14:27:29 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 35275 invoked by uid 500); 22 May 2008 14:27:28 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 35264 invoked by uid 99); 22 May 2008 14:27:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 May 2008 07:27:28 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates 209.85.146.177 as permitted sender) Received: from [209.85.146.177] (HELO wa-out-1112.google.com) (209.85.146.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 May 2008 14:26:40 +0000 Received: by wa-out-1112.google.com with SMTP id k17so80378waf.0 for ; Thu, 22 May 2008 07:26:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=JsbFZo7wrUGY4ZZU40zTvM2KOJXbZlA1vWXS2ROJQTc=; b=gYNV1iV9Z6AeoMHvW3up9mZLk2R8FnFRAxgRWwdUBt2SYinEo+91v0/axBIL1DydIZb6Vuud2EcQz6UL3c1vuboDtokBK3CzUt6RzsWhg9Pg3hRDf6H48r71MuTcdqPncVy+HUtxPt6gXHiZdwzPk3sIn3/ayt/lTGSW8Jmv2eI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=g1pg6Fyof8bkLA7pvJQbK9NpHYBROD8D3n1ALrMY/Y9ysF9dd62fP96hoxF343W+7EQy/H0K3acE/KcALEYVXqL2f7QwDd2OhZkD3Wc9YB1ePZiQWRLC+LZ4ueaGGobkAf08rQmPGol5hFt47ac0PknFHKs6Fv/S4JHZBqk30YQ= Received: by 10.114.60.19 with SMTP id i19mr144384waa.155.1211466416621; Thu, 22 May 2008 07:26:56 -0700 (PDT) Received: by 10.114.160.2 with HTTP; Thu, 22 May 2008 07:26:56 -0700 (PDT) Message-ID: Date: Thu, 22 May 2008 10:26:56 -0400 From: "Hiram Chirino" Sender: chirino@gmail.com To: users@activemq.apache.org Subject: Re: Looking for "encoded string too long" workaround In-Reply-To: <17401928.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <17401928.post@talk.nabble.com> X-Google-Sender-Auth: d6e3d0d70ceac439 X-Virus-Checked: Checked by ClamAV on apache.org The body of a TextMessage supports big strings. On Thu, May 22, 2008 at 7:05 AM, rtsan wrote: > > Hello, > > I need to send over http/https strings or objects bigger than 65k. Does > anyone know if there's a work-around or solution to "UTFDataFormatException: > encoded string too long" problem? > > Thanks in advance, > rtsan > > -- > View this message in context: http://www.nabble.com/Looking-for-%22encoded-string-too-long%22-workaround-tp17401928s2354p17401928.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com