Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of sully6768@gmail.com
 designates 209.85.223.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5yN=ygdYM7g_TthaRutg+x69XWvfFth0+CFx5CkwozVayOg@mail.gmail.com>
References: <1387296365444-5744954.post@n5.nabble.com>
	<CAGB5yN=ygdYM7g_TthaRutg+x69XWvfFth0+CFx5CkwozVayOg@mail.gmail.com>
Date: Fri, 20 Dec 2013 15:53:53 -0600
Message-ID: 
 <CANZYW6Zn9ZYsjChjALJo_DceraG69J+22LGJX2Tg7do0DXrw0Q@mail.gmail.com>
Subject: Re: Acknowledgement to JMS Topic on activemq
From: Scott England-Sullivan <sully6768@gmail.com>
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: multipart/alternative; boundary=20cf302234d56fc74504edfe5011

--20cf302234d56fc74504edfe5011
Content-Type: text/plain; charset=ISO-8859-1

A couple of additional notes:

Camel SJMS does have an issue identified with the aggregator and JMS
transactions.  SJMS is currently closing the transaction, batch included,
as the messages pass through the route.  It doesn't recognize the fact that
an aggregator is participating in the route which is effectively holding
copies of the messages.  This gap can cause a loss of messages should there
be a failure in the aggregator if the batch number has been met.  I am
going to be looking at this over the break and hopefully come up with a
solution.

I will be spending my down time over the holidays taking a look at this
issue to see if it can be be solved before the introduction of JTA to the
Camel project.

Best Regards,
Scott ES


On Wed, Dec 18, 2013 at 2:00 AM, Claus Ibsen <claus.ibsen@gmail.com> wrote:

> You can use transacted acknowledge mode with the camel-jms component.
>
> Just set transacted=true, and setup the TX stuff.
> http://camel.apache.org/jms
> http://camel.apache.org/transactional-client.html
>
> Mind that camel-jms only supports one message at a time, eg consume
> one message in a TX.
>
> The other camel-sjms has some support for batch consuming, but this
> component is not as hardened as the camel-jms one.
>
>
> On Tue, Dec 17, 2013 at 5:06 PM, Sri <sri.tech97@googlemail.com> wrote:
> > Hi All,
> >
> > I am consuming message from a topic and wanted send it to SOLR server as
> a
> > batch for a commit as committing on SOLR is expensive operation. How
> ever I
> > wanted to keep the message on the topic till the commit operation
> completes
> > successfully. I want to send successful acknowledgement in that case
> > otherwise no acknowledgement.
> >
> > I am using aggregator for batching the messages how ever I couldn't get
> any
> > hold acknowledgement. Aggregator sends successful acknowledgement as
> soon as
> > it reads from the topic.
> >
> > I do not want to loose any messages if by any chance SOLR doesn't commit
> > successfully.
> >
> > Your help will be much appreciated.
> >
> > Thanks
> > Sri
> >
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/Acknowledgement-to-JMS-Topic-on-activemq-tp5744954.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> Make your Camel applications look hawt, try: http://hawt.io
>


-- 
-- 
Scott England-Sullivan
Apache Camel Committer
Principal Consultant / Sr. Architect | Red Hat, Inc.
FuseSource is now part of Red Hat
Web:     fusesource.com <http://www.fusesource.com> |
redhat.com<http://www.redhat.com>
Blog:     sully6768.blogspot.com
Twitter: sully6768

--20cf302234d56fc74504edfe5011--