activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michel Van Hoof <mvh...@thisplays2.com>
Subject NMS / ActveMQ questions regarding network of brokers and ByteMessages.
Date Thu, 16 Jul 2009 08:03:45 GMT

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.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message