activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <>
Subject Re: Consuming a group of messages in a single transaction
Date Fri, 28 Jul 2006 08:30:48 GMT
At one point we were considering implementing an InputStreamMessage which
allowed a producer ship a consumer an 'InputStream'.  Basically the consumer
would only be able to read the input stream while the the producer is still
online.  The upside to this is that you get the benefits of sending the big
data out of band but still just using JMS network.

On 7/28/06, nlif <> wrote:
> Thanks, James.
> Sending just the URI is not an option in my case, since the participating
> applications do not share a file server (or a database, for that matter).
> As for the second suggestion, just to make sure I understand: do you mean
> that I should implement the equivalent of the ActiveMQ streams feature, by
> splliting the files into JMS ByteMessages and then include them in the
> MessageGroup and in the transaction? (btw I've looked at the Streams code,
> and I know this is pretty much what it does, only that the input stream
> auto-acknowledges each chunk, right?).
> Now, could there be a different approach to all of this? My whole problem
> stems from the fact I don't want to acknowledge ANY of the items (messages
> and/or files) until I have ALL of them. The reason is simple: if my
> cosumer
> crashes half-way, some data is lost. However, trying to sync the acks for
> all different items, that may be passed via different mechanisms, makes
> things very complicated for me.
> Is there another way? Is it possible to go back to simple MessageListeners
> and InputStream consumers, which acknowledge every item separately, but
> have
> a different mechanism for ensuring their  state is recoverable? Maybe I
> should go for a consumer that can persist its data? Or is this even harder
> to achieve?
> This seems to me like something many applications might require. Am I
> really
> the only one faced with a scenario in which a transmission is composed of
> several items, that cannot be sent as a single JMS message? Is there no
> generic solution for this?
> Naaman
> --
> View this message in context:
> Sent from the ActiveMQ - User forum at



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