Hi
You can have different queues for different styles
- queues which can safely be processed concurrently and out of order
- other queue(s) where messages must be processed in order
On Tue, Jan 31, 2012 at 11:00 AM, Hervé BARRAULT
wrote:
> Thanks for your accurate answers.
>
> I have seen mess
Thanks for your accurate answers.
I have seen messages groups but i have some messages which are out
potential groups.
So i have to deal with unordered messages. (or i should find a way to
have multiconsumer the main time and some time for some known messages
i should "downgrade" to only one cons
On Tue, Jan 31, 2012 at 10:00 AM, Hervé BARRAULT
wrote:
> Thanks,
> So, i should publish sequentially and can consume concurrently.
Yeah, or public concurrently also. If ordering does not matter.
Only if you need ordering of messages, and process concurrently you
can use message groups
http://ac
Thanks,
So, i should publish sequentially and can consume concurrently.
As there is only direct component which is a synchronous call, I guess
a transaction can work across multiple route but in one camel context.
Am i wrong ?
On 1/30/12, Claus Ibsen wrote:
> On Mon, Jan 30, 2012 at 3:41 PM, H
On Mon, Jan 30, 2012 at 3:41 PM, Hervé BARRAULT
wrote:
> Hi,
> thanks for the quick answer.
>
>> It does not support batching, not async TX, etc.
>
> But does it supports TX and concurrentConsumers ?
>
> I have to multiply the number of consumers as they are slower than the
> producer.
>
Yes.
Hi,
thanks for the quick answer.
> It does not support batching, not async TX, etc.
But does it supports TX and concurrentConsumers ?
I have to multiply the number of consumers as they are slower than the producer.
On 1/30/12, Claus Ibsen wrote:
> On Mon, Jan 30, 2012 at 11:05 AM, Hervé BARRA
On Mon, Jan 30, 2012 at 11:05 AM, Hervé BARRAULT
wrote:
> Hi, thanks for confirmation.
> So for publication, i should use a transactions with sequential mechanism.
>
> I have seen also on activeMQ documentation :
> http://activemq.apache.org/should-i-use-transactions.html :
> Its also worth noting
Hi, thanks for confirmation.
So for publication, i should use a transactions with sequential mechanism.
I have seen also on activeMQ documentation :
http://activemq.apache.org/should-i-use-transactions.html :
Its also worth noting that if you are using persistent messaging, the
fastest way of usin
Spring Transaction does not support using multiple threads. The
transactional work should be done in the same thread, from spring TX
manager point of view.
On Fri, Jan 27, 2012 at 5:29 PM, Hervé BARRAULT
wrote:
> Hi,
>
> I found in archive that parallel processing is not compatible with
> transa
Hi,
I found in archive that parallel processing is not compatible with transaction.
Is it still relevant or is there a workaround ?
Regards
Hervé
On 1/27/12, Hervé BARRAULT wrote:
> Hi,
>
> I have two question about a route, JMS and transactions.
>
> The use is : one request response Web serv
Hi,
I have two question about a route, JMS and transactions.
The use is : one request response Web service put message on n queues
(using transaction ensure the message really put in all queues or no
one).
Does this route make sense (only "pseudo" route not all the stuff to
manage transaction i
11 matches
Mail list logo
