Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 32596 invoked from network); 9 Aug 2008 23:51:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Aug 2008 23:51:56 -0000 Received: (qmail 8875 invoked by uid 500); 9 Aug 2008 23:51:54 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 8848 invoked by uid 500); 9 Aug 2008 23:51:54 -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 8837 invoked by uid 99); 9 Aug 2008 23:51:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Aug 2008 16:51:54 -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 tabish121@gmail.com designates 74.125.46.152 as permitted sender) Received: from [74.125.46.152] (HELO yw-out-1718.google.com) (74.125.46.152) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Aug 2008 23:50:56 +0000 Received: by yw-out-1718.google.com with SMTP id 6so666366ywa.86 for ; Sat, 09 Aug 2008 16:51:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=mQDlar3D2aJOtyDg10si3zWW4MJGkP9c5SuTOSvjtKg=; b=GqabLLnhpg1zGHBiK+F199gYb5leCC5ylag5KhqIgMgUZnxCPg/pFEvTvGa40Ou1rY I93OGY1996ulxnoAcxJdrS1cv0NIB31UvRU9WxyZC0I5U6u2wGmqn+euaDsy97VIQbiE gvK9BMlzg775jGCEPkYk2OHseKPh0rkAsvDCM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=lnm21nVjknIcSZezqTQ9ZQSF9PVW1ITVOxlGJJHebpdlYYD1USFZ5MZ11qcsK+GPXN zqWgsXQPqP0HJWUf0i7yDw08+8caU3CS4xdXNKrg94KLxqTo3566sHhC/E3Dm6z5fykr A59AbOmjWuNR5TBh6o5qOrmzP1oPxNBhXGLow= Received: by 10.150.11.6 with SMTP id 6mr9733895ybk.9.1218325866304; Sat, 09 Aug 2008 16:51:06 -0700 (PDT) Received: from ?192.168.2.150? ( [98.218.84.158]) by mx.google.com with ESMTPS id 4sm2721697yxq.8.2008.08.09.16.51.04 (version=SSLv3 cipher=RC4-MD5); Sat, 09 Aug 2008 16:51:05 -0700 (PDT) Subject: Re: CMS - setStringProperty() max length From: Timothy Bish To: users@activemq.apache.org In-Reply-To: <18577838.post@talk.nabble.com> References: <18577838.post@talk.nabble.com> Content-Type: text/plain Date: Sat, 09 Aug 2008 19:48:10 -0400 Message-Id: <1218325690.27523.13.camel@office> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I've run this a couple times, definitely something odd there, looks like the message gets marshaled and sent but the broker never acknowledges having received it, its possible we are messing up the marshaled data, we will need to investigate this one further. Regards Tim. On Mon, 2008-07-21 at 14:21 -0700, FastEddie wrote: > I'm using a TextMessage, and also setting a StringProperty on it. > > What is the max size of the StringProperty? > > I noticed in this thread, that the max size of the TextMessage itself can be > up to 2gb: > http://www.nabble.com/TextMessage-vs-ByteMessage-vs-StreamMessage-td16755490.html > > And I am able to send TextMessages with large strings as the TextMessage > text. > > But when I set a StringProperty with a large string, it gives an exception. > > I'm using CMS, and you can see this behavior with a simple modification to > src\examples\main.cpp: > > // Create a messages > string text = (string)"Hello world! from thread " + threadIdStr; > > string textProperty; > textProperty.assign( 32800, 'z' ); > > for( int ix=0; ix TextMessage* message = session->createTextMessage( text ); > > message->setIntProperty( "Integer", ix ); > message->setStringProperty( "zzzzz", textProperty ); > > // Tell the producer to send the message > printf( "Sent message #%d from thread %s\n", ix+1, threadIdStr.c_str() ); > producer->send( message ); > > delete message; > } > > > > So, my question is, why is there a string size limit on the StringProperty, > but not on the TextMessage itself? And what are my alternatives? > > Thanks in advance