Hi, just wondering why the sjms-batch component was removed in camel 3.** and
when will it be reimplemented? thanks
i'm using sjms-batch consumer with activemq, when consuming around 1.5 million
messages, the last 400 or so messages seemed to be always stuck in the queue.
nothing is going on with them, any ideas what could have caused such behavior?
thanks
Hi, i am using sjms batch and during volume testing, there are bunch of
messages going to the dead letter queue with the following, any ideas why?
thanks
Unknown message type [org.apache.activemq.command.ActiveMQMessage]
ActiveMQMessage {commandId = 16, responseRequired = true, messageId
found out the stuck messages were actually duplicate messages since I was
using indempotentrepository, my question is how do i reroute these messages to
another queue if possible? thanks
On Friday, July 17, 2020, 02:26:40 PM EDT, Bing Lu
wrote:
Hi, I'm using sjms batch with act
Hi, I'm using sjms batch with activemq, the consumers processes messages on
the queue and after a while, there is nothing going to the consumers and no
errors in the log while some messages are still stuck on the queue. any ideas
what could have caused this?
i have the activemqconne
the
>>> >> route continues, but the route ends there, so it will then commit. And
>>> >> on the same time the aggregator runs in parallel (independent) and
>>> >> aggregate messages and then when they are completed, then trigger the
>>> >&g
t; aggregate messages and then when they are completed, then trigger the
>> >> message to be routed independent, but that is routed outside a
>> >> transaction.
>> >>
>> >> So if you aim to batch N JMS messages into a single aggregate in the
>> >
While testing with SJMS-Batch, I replaced my own aggregateStrategy with the
GroupedExchangeStrategy from camel and was surprised to see that the
messages are all null. GetBody == null, Exchange.GROUPED_EXCHANGE == null.
Any Idea why?
Thx.
-
Guile Newbie
--
View this message in context
From what i can tell, the sjms component doesn’t support sending batch messages
with the InOut ExchangePattern ?
The InOnly producer seems to do it right, by casting the message body to a
Collection, where the InOutProducer simply calls makeJmsMessage()
I looked over the documentation, but can’t