Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <24694944.post@talk.nabble.com>
Date: Tue, 28 Jul 2009 01:42:27 -0700 (PDT)
From: Michel Van Hoof <mvhoof@thisplays2.com>
To: users@activemq.apache.org
Subject: Re: NMS / ActveMQ questions regarding network of brokers and
  ByteMessages.
In-Reply-To: <5a56ce1b0907272218gf8aef2cud23721b460d1e3b5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <24512112.post@talk.nabble.com>
 <5a56ce1b0907272218gf8aef2cud23721b460d1e3b5@mail.gmail.com>


true, however some smaller files, we would like to send through the MQ for
ensured delivery. The local MQ in the network of brokers could the be the
single point of access to the net (url) instead of the client. Or would in
the case of the blob, the client still require access to the url ? 


semog wrote:
> 
> NMS does not support the BlobMessage, but if you can access the large
> files
> via a URL, then could you just send a TextMessage with the URL?
> 
> On Thu, Jul 16, 2009 at 1:03 AM, Michel Van Hoof
> <mvhoof@thisplays2.com>wrote:
> 
>>
>> Hi,
>>
>> After reading just about every article, documentation and forum about
>> ActiveMQ / NMS the last couple of weeks, a couple of things are still
>> unclear so i was hoping someone here could enlighten me :s
>>
>> ByteMessages
>>
>> We are looking at a situation where a lot of files between 5 to 200Mb
>> (ocasionally more but is seldom) should be sent through the MQ. These
>> 'messages' could be present in a queue for a long while (multiple days)
>> since the clients are bandwidth restricted for their downloads. A network
>> of
>> brokers would be in place ( unrestricted ) to get the message as close as
>> possible to the client.
>>
>> Now i know the standard is: "for long term storage, use a database", but
>> this would create a lot of overhead in our enviroment ..
>>
>> Now my question is: what is the best way to configure ActiveMQ for this
>> without killing the machine(s) ? We would use PostGresql as JDBC journal
>> but
>> should we cache the messages locally on disk too ? Will ActiveMQ keep
>> these
>> messages in memory ? Can we avoid this ? Can we make sure new messages
>> would
>> still arrive in the queue even if it has multiple 100's of MB's in queue
>> for
>> that specific client ? Does NMS support the "BlobMessage" so we could
>> just
>> pass a url ( all files are already hosted)
>>
>> thanks !
>> --
>> View this message in context:
>> http://www.nabble.com/NMS---ActveMQ-questions-regarding-network-of-brokers-and-ByteMessages.-tp24512112p24512112.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/NMS---ActveMQ-questions-regarding-network-of-brokers-and-ByteMessages.-tp24512112p24694944.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.